[COMMITTERS] slony1-ctl - slony-ctl: Oups, I forgot the Changelog...
Log Message: --- Oups, I forgot the Changelog... Modified Files: -- slony-ctl/etc: bases.h (r1.5 - r1.6) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/slony1-ctl/slony-ctl/etc/bases.h?r1=1.5r2=1.6) relations.h (r1.6 - r1.7) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/slony1-ctl/slony-ctl/etc/relations.h?r1=1.6r2=1.7) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: More fixes for shutdown during recovery.
Log Message: --- More fixes for shutdown during recovery. 1. If we receive a fast shutdown request while in the PM_STARTUP state, process it just as we would in PM_RECOVERY, PM_HOT_STANDBY, or PM_RUN. Without this change, an early fast shutdown followed by Hot Standby causes the database to get stuck in a state where a shutdown is pending (so no new connections are allowed) but the shutdown request is never processed unless we end Hot Standby and enter normal running. 2. Avoid removing the backup label file when a smart or fast shutdown occurs during recovery. It makes sense to do this once we've reached normal running, since we must be taking a backup which now won't be valid. But during recovery we must be recovering from a previously taken backup, and any backup label file is needed to restart recovery from the right place. Fujii Masao and Robert Haas Modified Files: -- pgsql/src/backend/postmaster: postmaster.c (r1.608 - r1.609) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/postmaster/postmaster.c?r1=1.608r2=1.609) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] psqlodbc - psqlodbc: 1.
Log Message: --- 1. Use poll() instead of select() when it's available. 2. Take comments or line comments in a query into account. 3. Fix a crash bug on authentication failures. Modified Files: -- psqlodbc: configure.ac (r1.86 - r1.87) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/psqlodbc/psqlodbc/configure.ac?r1=1.86r2=1.87) connection.c (r1.187 - r1.188) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/psqlodbc/psqlodbc/connection.c?r1=1.187r2=1.188) convert.c (r1.187 - r1.188) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/psqlodbc/psqlodbc/convert.c?r1=1.187r2=1.188) socket.c (r1.70 - r1.71) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/psqlodbc/psqlodbc/socket.c?r1=1.70r2=1.71) socket.h (r1.44 - r1.45) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/psqlodbc/psqlodbc/socket.h?r1=1.44r2=1.45) statement.c (r1.146 - r1.147) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/psqlodbc/psqlodbc/statement.c?r1=1.146r2=1.147) version.h (r1.156 - r1.157) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/psqlodbc/psqlodbc/version.h?r1=1.156r2=1.157) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Tell openssl to include the names of the root certs the server
Log Message: --- Tell openssl to include the names of the root certs the server trusts in requests for client certs. This lets a client with a keystore select the appropriate client certificate to send. In particular, this is necessary to get Java clients to work in all but the most trivial configurations. Per discussion of bug #5468. Craig Ringer Modified Files: -- pgsql/src/backend/libpq: be-secure.c (r1.99 - r1.100) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/libpq/be-secure.c?r1=1.99r2=1.100) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] psqlodbc - psqlodbc: Change the release note.(prep release)
Log Message: --- Change the release note.(prep release) Modified Files: -- psqlodbc/docs: release.html (r1.60 - r1.61) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/psqlodbc/psqlodbc/docs/release.html?r1=1.60r2=1.61) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Minor editorialization for be-secure.c: fix comments and some
Log Message: --- Minor editorialization for be-secure.c: fix comments and some formatting infelicities. Modified Files: -- pgsql/src/backend/libpq: be-secure.c (r1.100 - r1.101) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/libpq/be-secure.c?r1=1.100r2=1.101) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: The message style police pay a visit to hba.c.
Log Message: --- The message style police pay a visit to hba.c. Modified Files: -- pgsql/src/backend/libpq: hba.c (r1.206 - r1.207) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/libpq/hba.c?r1=1.206r2=1.207) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Fix psql help: \da+ is same as \da, but \daS is not.
Log Message: --- Fix psql help: \da+ is same as \da, but \daS is not. Noted by Stephen Frost. Modified Files: -- pgsql/src/bin/psql: help.c (r1.158 - r1.159) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/help.c?r1=1.158r2=1.159) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: HS Defer buffer pin deadlock check until deadlock_timeout has
Log Message: --- HS Defer buffer pin deadlock check until deadlock_timeout has expired. During Hot Standby we need to check for buffer pin deadlocks when the Startup process begins to wait, in case it never wakes up again. We previously made the deadlock check immediately on the basis it was cheap, though clearer thinking and prima facie evidence shows that was too simple. Refactor existing code to make it easy to add in deferral of deadlock check until deadlock_timeout allowing a good reduction in deadlock checks since far few buffer pins are held for that duration. It's worth doing anyway, though major goal is to prevent further reports of context switching with high numbers of users on occasional tests. Modified Files: -- pgsql/src/backend/storage/ipc: standby.c (r1.23 - r1.24) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/storage/ipc/standby.c?r1=1.23r2=1.24) pgsql/src/backend/storage/lmgr: proc.c (r1.218 - r1.219) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/storage/lmgr/proc.c?r1=1.218r2=1.219) pgsql/src/include/storage: proc.h (r1.121 - r1.122) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/storage/proc.h?r1=1.121r2=1.122) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Fix bogus error message for SSL-cert authentication, due to lack
Log Message: --- Fix bogus error message for SSL-cert authentication, due to lack of a uaCert entry in auth_failed(). Put the switch entries into a sane order, namely the one the enum is declared in. Modified Files: -- pgsql/src/backend/libpq: auth.c (r1.200 - r1.201) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/libpq/auth.c?r1=1.200r2=1.201) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Rearrange libpq's SSL initialization to simplify it and make it
Log Message: --- Rearrange libpq's SSL initialization to simplify it and make it handle some additional cases correctly. The original coding failed to load additional (chain) certificates from the client cert file, meaning that indirectly signed client certificates didn't work unless one hacked the server's root.crt file to include intermediate CAs (not the desired approach). Another problem was that everything got loaded into the shared SSL_context object, which meant that concurrent connections trying to use different sslcert settings could well fail due to conflicting over the single available slot for a keyed certificate. To fix, get rid of the use of SSL_CTX_set_client_cert_cb(), which is deprecated anyway in the OpenSSL documentation, and instead just unconditionally load the client cert and private key during connection initialization. This lets us use SSL_CTX_use_certificate_chain_file(), which does the right thing with additional certs, and is lots simpler than the previous hacking about with BIO-level access. A small disadvantage is that we have to load the primary client cert a second time with SSL_use_certificate_file, so that that one ends up in the correct slot within the connection's SSL object where it can get paired with the key. Given the other overhead of making an SSL connection, that doesn't seem worth worrying about. Per discussion ensuing from bug #5468. Modified Files: -- pgsql/src/interfaces/libpq: fe-connect.c (r1.392 - r1.393) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/libpq/fe-connect.c?r1=1.392r2=1.393) fe-secure.c (r1.133 - r1.134) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/libpq/fe-secure.c?r1=1.133r2=1.134) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: In walsender, don't sleep if there's outstanding WAL waiting to
Log Message: --- In walsender, don't sleep if there's outstanding WAL waiting to be sent, otherwise we effectively rate-limit the streaming as pointed out by Simon Riggs. Also, send the WAL in smaller chunks, to respond to signals more promptly. Modified Files: -- pgsql/src/backend/replication: walsender.c (r1.20 - r1.21) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/replication/walsender.c?r1=1.20r2=1.21) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Thinko in previous commit: ensure that MAX_SEND_SIZE is always
Log Message: --- Thinko in previous commit: ensure that MAX_SEND_SIZE is always greater than XLOG_BLCKSZ, by defining it as 16 * XLOG_BLCKSZ rather than directly as 128k bytes. Modified Files: -- pgsql/src/backend/replication: walsender.c (r1.21 - r1.22) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/replication/walsender.c?r1=1.21r2=1.22) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Document pgFouine and check_postgres as log analysis options.
Log Message: --- Document pgFouine and check_postgres as log analysis options. Modified Files: -- pgsql/doc/src/sgml: maintenance.sgml (r1.103 - r1.104) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/maintenance.sgml?r1=1.103r2=1.104) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Improve SSL-related documentation.
Log Message: --- Improve SSL-related documentation. Explain how to deal with certificate chains, do assorted wordsmithing. Modified Files: -- pgsql/doc/src/sgml: client-auth.sgml (r1.137 - r1.138) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/client-auth.sgml?r1=1.137r2=1.138) config.sgml (r1.278 - r1.279) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/config.sgml?r1=1.278r2=1.279) libpq.sgml (r1.305 - r1.306) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/libpq.sgml?r1=1.305r2=1.306) runtime.sgml (r1.435 - r1.436) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/runtime.sgml?r1=1.435r2=1.436) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Fix SGML markup
Log Message: --- Fix SGML markup Modified Files: -- pgsql/doc/src/sgml: maintenance.sgml (r1.104 - r1.105) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/maintenance.sgml?r1=1.104r2=1.105) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Adjust comment to reflect that we now have Hot Standby.
Log Message: --- Adjust comment to reflect that we now have Hot Standby. Pointed out by Robert Haas. Modified Files: -- pgsql/src/backend/access/transam: xlog.c (r1.413 - r1.414) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/transam/xlog.c?r1=1.413r2=1.414) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Avoid starting walreceiver in states where it shouldn't be
Log Message: --- Avoid starting walreceiver in states where it shouldn't be running. In particular, it's bad to start walreceiver when in state PM_WAIT_BACKENDS, because we have no provision to kill walreceiver when in that state. Fujii Masao Modified Files: -- pgsql/src/backend/postmaster: postmaster.c (r1.609 - r1.610) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/postmaster/postmaster.c?r1=1.609r2=1.610) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
