- 23 Feb, 2002 1 commit
-
-
Peter Eisentraut authored
any order without affecting results.
-
- 19 Feb, 2002 2 commits
- 10 Jan, 2002 1 commit
-
-
Tom Lane authored
pgsql-hackers discussion of this date.
-
- 06 Jan, 2002 1 commit
-
-
Tom Lane authored
to the client before closing the connection. Before 7.2 this was done correctly, but new code would simply close the connection with no report to the client.
-
- 04 Dec, 2001 1 commit
-
-
Tom Lane authored
per recent pghackers discussions. Improving this should be a TODO for 7.3.
-
- 12 Nov, 2001 1 commit
-
-
Tom Lane authored
-
- 11 Nov, 2001 1 commit
-
-
Tom Lane authored
a NULL pointer. Per report from Stephen Pillinger 8-Nov-01.
-
- 10 Nov, 2001 1 commit
-
-
Tom Lane authored
per suggestion from Peter.
-
- 06 Nov, 2001 1 commit
-
-
Tom Lane authored
are correct, consistent, and complete ... motivated by gripe from Oliver Elphick, but I see someone had already made an incomplete stab at this.
-
- 05 Nov, 2001 1 commit
-
-
Bruce Momjian authored
initdb/regression tests pass.
-
- 04 Nov, 2001 2 commits
-
-
Tom Lane authored
-
Tom Lane authored
so that only one signal number is used not three. Flags in shared memory tell the reason(s) for the current signal. This method is extensible to handle more signal reasons without chewing up even more signal numbers, but the immediate reason is to keep pg_pwd reloads separate from SIGHUP processing in the postmaster. Also clean up some problems in the postmaster with delayed response to checkpoint status changes --- basically, it wouldn't schedule a checkpoint if it wasn't getting connection requests on a regular basis.
-
- 02 Nov, 2001 1 commit
-
-
Tom Lane authored
postmaster children before client auth step. Postmaster now rereads pg_pwd on receipt of SIGHUP, the same way that pg_hba.conf is handled. No cycles need be expended to validate password cache validity during connection startup.
-
- 28 Oct, 2001 1 commit
-
-
Bruce Momjian authored
spacing. Also adds space for one-line comments.
-
- 25 Oct, 2001 1 commit
-
-
Bruce Momjian authored
tests pass.
-
- 22 Oct, 2001 1 commit
-
-
Tom Lane authored
environment strings need to be moved around, do so when called from initial startup (main.c), not in init_ps_status. This eliminates the former risk of invalidating saved environment-string pointers, since no code has yet had a chance to grab any such pointers when main.c is running.
-
- 21 Oct, 2001 1 commit
-
-
Tom Lane authored
per suggestion from Peter. Simplify several APIs by transmitting the original argv location directly from main.c to ps_status.c, instead of passing it down through several levels of subroutines.
-
- 19 Oct, 2001 4 commits
-
-
Tom Lane authored
before.
-
Tom Lane authored
subprocesses; perhaps this will fix portability problem just noted by Lockhart. Also, move test for bad permissions of DataDir to a more logical place.
-
Tom Lane authored
bootstrap) check for a valid PG_VERSION file before looking at anything else in the data directory. This fixes confusing error report when trying to start current sources in a pre-7.1 data directory. Per trouble report from Rich Shepard 10/18/01.
-
Tom Lane authored
just after receipt of the startup packet. Now, postmaster children that are waiting for client authentication response will show as 'postgres: user database host authentication'. Also, do an init_ps_display for startup/shutdown/checkpoint subprocesses, so that they are readily identifiable as well. Fix an obscure race condition that could lead to Assert failure in the postmaster --- attempting to start a checkpoint process before any connections have been received led to calling PostmasterRandom before setting random_seed.
-
- 03 Oct, 2001 1 commit
-
-
Tom Lane authored
format strings wherever possible. Remarkably, this exercise didn't turn up any inconsistencies, but it seems a good idea for the future.
-
- 30 Sep, 2001 1 commit
-
-
Tom Lane authored
postmaster ... it should not be set in the postmaster itself.
-
- 21 Sep, 2001 2 commits
-
-
Tom Lane authored
(salts were always zero!?), add much missing documentation.
-
Tom Lane authored
a hung client or lost connection can't indefinitely block a postmaster child (not to mention the possibility of deliberate DoS attacks). Timeout is controlled by new authentication_timeout GUC variable, which I set to 60 seconds by default ... does that seem reasonable?
-
- 08 Sep, 2001 1 commit
-
-
Tom Lane authored
We will no longer try to send elog messages to the client before we have initialized backend libpq (oops); however, reporting bogus commandline switches via elog does work now (not irrelevant, because of PGOPTIONS). Fix problem with inappropriate sending of checkpoint-process messages to stderr.
-
- 07 Sep, 2001 3 commits
-
-
Jan Wieck authored
the postmaster can kill the forked off processes when shutdown is requested. Jan
-
Tom Lane authored
max_connections.
-
Tom Lane authored
for them, and making them just wastes time during backend startup/shutdown. Also, remove compile-time MAXBACKENDS limit per long-ago proposal. You can now set MaxBackends as high as your kernel can stand without any reconfiguration/recompilation.
-
- 30 Aug, 2001 1 commit
-
-
Peter Eisentraut authored
-
- 17 Aug, 2001 1 commit
-
-
Bruce Momjian authored
-
- 05 Aug, 2001 1 commit
-
-
Tom Lane authored
Make sure it exits immediately when collector process dies --- in old code, buffer process would hang around and compete with the new buffer process for packets. Make sure it doesn't block on writing the pipe when the collector falls more than a pipeload behind. Avoid leaking pgstats FDs into every backend.
-
- 04 Aug, 2001 1 commit
-
-
Tom Lane authored
platforms system(2) gets confused unless the signal handler is set to SIG_DFL, not SIG_IGN. pgstats.c now uses pqsignal() as it should, not signal(). Also, arrange for the stats collector process to show a reasonable ID in 'ps', rather than looking like a postmaster.
-
- 31 Jul, 2001 1 commit
-
-
Tom Lane authored
number in the data structure so that we can give at least a minimally useful idea of where the mistake is when we issue syntax error messages. Move the ClientAuthentication() call to where it should have been in the first place, so that postmaster memory releasing can happen in a reasonable place also. Update obsolete comments, correct one real bug (auth_argument was not picked up correctly).
-
- 30 Jul, 2001 1 commit
-
-
Bruce Momjian authored
Lists, and use that for user validation. Bruce Momjian
-
- 03 Jul, 2001 1 commit
-
-
Tom Lane authored
to start it before we have acquired the data directory lock; also a bad idea to start it before we have set up to catch SIGCHLD signals.
-
- 01 Jul, 2001 1 commit
-
-
Tom Lane authored
immediately, we will fork a child even if the database state does not permit connections to be accepted (eg, we are in recovery mode). The child process will correctly reject the connection and exit as soon as it's finished collecting the connection request message. However, this means that reaper() must be prepared to see child process exit signals even while it's waiting for startup or shutdown process to finish. As was, a connection request arriving during a database recovery or shutdown would cause postmaster abort.
-
- 29 Jun, 2001 1 commit
-
-
Tom Lane authored
-
- 25 Jun, 2001 1 commit
-
-
Tom Lane authored
directly, rather than through SetConfigOption().
-