pgsql/src/backend/main (main.c)

pgsql/src/backend/main (main.c)

Post by t.. » Mon, 01 Jan 2001 12:34:30




Author: tgl

Update of /home/projects/pgsql/cvsroot/pgsql/src/backend/main
     from hub.org:/home/projects/pgsql/tmp/cvs-serv59374/backend/main

Modified Files:
        main.c

-----------------------------  Log Message  -----------------------------


 
 
 

pgsql/src/backend/main (main.c)

Post by t.. » Tue, 02 Jan 2001 03:04:53



Author: tgl

Update of /home/projects/pgsql/cvsroot/pgsql/src/backend/main
     from hub.org:/home/projects/pgsql/tmp/cvs-serv2516

Modified Files:
        main.c

-----------------------------  Log Message  -----------------------------

Reverse #if test to be defined(__osf__) rather than not-any-of-a-lot-
of-others.

 
 
 

1. pgsql/src/backend/main main.c

CVSROOT:        /home/projects/pgsql/cvsroot
Module name:    pgsql

Modified files:
        src/backend/main: main.c

Log message:
        attached is take-2 of a patch which fixes a bug related
        to the use of getpwuid when running in standalone mode.
        this patch allocates some persistent storage (using
        strdup) to store the username obtained with getpwuid
        in src/backend/main/main.c.  this is necessary because
        later on, getpwuid is called again (in ValidateBinary).

        the man pages for getpwuid on SCO OpenServer, FreeBSD,
        and Darwin all have words to this effect (this is from
        the SCO OpenServer man page):

        Note
        ====
        All information is contained in a static area, so it must
        be copied if it is to be saved. Otherwise, it may be
        overwritten on subsequent calls to these routines.

        in particular, on my platform, the storage used to hold
        the pw_name from the first call is overwritten such that
        it looks like an empty username.  this causes a problem
        later on in SetSessionUserIdFromUserName.

        i'd assume this isn't a problem on most platforms because
        getpwuid is called with the same UID both times, and the
        same thing ends up happening to that static storage each
        time.  however, that's not guaranteed, and is _not_ what
        happens on my platform (at least :).

        this is for the version of 7.1 available via anon cvs as
        of Tue Jan 23 15:14:00 2001 PST:
        .../src/backend/main/main.c,v 1.37 2000/12/31 18:04:35 tgl Exp


2. Problems to Restore SQL Server

3. pgsql/src/backend/main (main.c)

4. split string and insert into temp table

5. Replication simultaneously

6. Putting code in main of src/backend/main/main.c

7. sysprocplan Locking?

8. pgsql-server/src/backend/main main.c

9. forking child processes in src/backend/main/main.c

10. patch for src/backend/main/main.ch

11. patch for src/backend/main/main.c