[COMMITTERS] pgsql: Avoid using unnecessary pgwin32_safestat in libpq.
Log Message: --- Avoid using unnecessary pgwin32_safestat in libpq. Modified Files: -- pgsql/src/include: port.h (r1.120 -> r1.121) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/port.h?r1=1.120&r2=1.121) pgsql/src/interfaces/libpq: Makefile (r1.165 -> r1.166) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/libpq/Makefile?r1=1.165&r2=1.166) pgsql/src/tools/msvc: Mkvcbuild.pm (r1.26 -> r1.27) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/tools/msvc/Mkvcbuild.pm?r1=1.26&r2=1.27) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Avoid using unnecessary pgwin32_safestat in libpq.
Log Message: --- Avoid using unnecessary pgwin32_safestat in libpq. Tags: REL8_3_STABLE Modified Files: -- pgsql/src/include: port.h (r1.116.2.3 -> r1.116.2.4) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/port.h?r1=1.116.2.3&r2=1.116.2.4) pgsql/src/interfaces/libpq: Makefile (r1.159.2.1 -> r1.159.2.2) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/libpq/Makefile?r1=1.159.2.1&r2=1.159.2.2) pgsql/src/tools/msvc: Mkvcbuild.pm (r1.25.2.1 -> r1.25.2.2) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/tools/msvc/Mkvcbuild.pm?r1=1.25.2.1&r2=1.25.2.2) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Avoid using unnecessary pgwin32_safestat in libpq.
Log Message: --- Avoid using unnecessary pgwin32_safestat in libpq. Tags: REL8_2_STABLE Modified Files: -- pgsql/src/include: port.h (r1.106.2.5 -> r1.106.2.6) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/port.h?r1=1.106.2.5&r2=1.106.2.6) pgsql/src/interfaces/libpq: Makefile (r1.149.2.3 -> r1.149.2.4) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/libpq/Makefile?r1=1.149.2.3&r2=1.149.2.4) pgsql/src/tools/msvc: mkvcbuild.pl (r1.8 -> r1.8.2.1) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/tools/msvc/mkvcbuild.pl?r1=1.8&r2=1.8.2.1) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Add to TODO: > * Implement the non-threaded Avahi service
Log Message: --- Add to TODO: > * Implement the non-threaded Avahi service discovery protocol > http://archives.postgresql.org/pgsql-hackers/2008-02/msg00939.php > http://archives.postgresql.org/pgsql-patches/2008-02/msg00097.php > http://archives.postgresql.org/pgsql-hackers/2008-03/msg01211.php > http://archives.postgresql.org/pgsql-patches/2008-04/msg1.php Modified Files: -- pgsql/doc: TODO (r1.2422 -> r1.2423) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/TODO?r1=1.2422&r2=1.2423) pgsql/doc/src/FAQ: TODO.html (r1.928 -> r1.929) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/TODO.html?r1=1.928&r2=1.929) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Update TODO wording.
Log Message: --- Update TODO wording. Modified Files: -- pgsql/doc: TODO (r1.2423 -> r1.2424) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/TODO?r1=1.2423&r2=1.2424) pgsql/doc/src/FAQ: TODO.html (r1.929 -> r1.930) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/TODO.html?r1=1.929&r2=1.930) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Fix comment typo.
Log Message: --- Fix comment typo. Bryce Nesbitt Modified Files: -- pgsql/src/bin/psql: mbprint.c (r1.29 -> r1.30) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/mbprint.c?r1=1.29&r2=1.30) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Fix LOAD_CRIT_INDEX() macro to take out AccessShareLock on the
Log Message: --- Fix LOAD_CRIT_INDEX() macro to take out AccessShareLock on the system index it is trying to build a relcache entry for. This is an oversight in my 8.2 patch that tried to ensure we always took a lock on a relation before trying to build its relcache entry. The implication is that if someone committed a reindex of a critical system index at about the same time that some other backend were starting up without a valid pg_internal.init file, the second one might PANIC due to not seeing any valid version of the index's pg_class row. Improbable case, but definitely not impossible. Modified Files: -- pgsql/src/backend/utils/cache: relcache.c (r1.270 -> r1.271) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/cache/relcache.c?r1=1.270&r2=1.271) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Fix LOAD_CRIT_INDEX() macro to take out AccessShareLock on the
Log Message: --- Fix LOAD_CRIT_INDEX() macro to take out AccessShareLock on the system index it is trying to build a relcache entry for. This is an oversight in my 8.2 patch that tried to ensure we always took a lock on a relation before trying to build its relcache entry. The implication is that if someone committed a reindex of a critical system index at about the same time that some other backend were starting up without a valid pg_internal.init file, the second one might PANIC due to not seeing any valid version of the index's pg_class row. Improbable case, but definitely not impossible. Tags: REL8_3_STABLE Modified Files: -- pgsql/src/backend/utils/cache: relcache.c (r1.266.2.2 -> r1.266.2.3) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/cache/relcache.c?r1=1.266.2.2&r2=1.266.2.3) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Fix LOAD_CRIT_INDEX() macro to take out AccessShareLock on the
Log Message: --- Fix LOAD_CRIT_INDEX() macro to take out AccessShareLock on the system index it is trying to build a relcache entry for. This is an oversight in my 8.2 patch that tried to ensure we always took a lock on a relation before trying to build its relcache entry. The implication is that if someone committed a reindex of a critical system index at about the same time that some other backend were starting up without a valid pg_internal.init file, the second one might PANIC due to not seeing any valid version of the index's pg_class row. Improbable case, but definitely not impossible. Tags: REL8_2_STABLE Modified Files: -- pgsql/src/backend/utils/cache: relcache.c (r1.250.2.1 -> r1.250.2.2) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/cache/relcache.c?r1=1.250.2.1&r2=1.250.2.2) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Update most recent release to 8.3.1.
Log Message: --- Update most recent release to 8.3.1. Modified Files: -- pgsql/doc: FAQ (r1.454 -> r1.455) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/FAQ?r1=1.454&r2=1.455) pgsql/doc/src/FAQ: FAQ.html (r1.411 -> r1.412) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/FAQ.html?r1=1.411&r2=1.412) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Ignore blank lines in typedef file.
Log Message: --- Ignore blank lines in typedef file. Modified Files: -- pgsql/src/tools/pgindent: pgindent (r1.98 -> r1.99) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/tools/pgindent/pgindent?r1=1.98&r2=1.99) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Fix MinGW warnings re formats and unused variables.
Log Message: --- Fix MinGW warnings re formats and unused variables. per ITAGAKI Takahiro Modified Files: -- pgsql/src/backend/port/win32: signal.c (r1.20 -> r1.21) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/port/win32/signal.c?r1=1.20&r2=1.21) pgsql/src/port: exec.c (r1.59 -> r1.60) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/port/exec.c?r1=1.59&r2=1.60) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Repair two places where SIGTERM exit could leave shared memory
Log Message: --- Repair two places where SIGTERM exit could leave shared memory state corrupted. (Neither is very important if SIGTERM is used to shut down the whole database cluster together, but there's a problem if someone tries to SIGTERM individual backends.) To do this, introduce new infrastructure macros PG_ENSURE_ERROR_CLEANUP/PG_END_ENSURE_ERROR_CLEANUP that take care of transiently pushing an on_shmem_exit cleanup hook. Also use this method for createdb cleanup --- that wasn't a shared-memory-corruption problem, but SIGTERM abort of createdb could leave orphaned files lying around. Backpatch as far as 8.2. The shmem corruption cases don't exist in 8.1, and the createdb usage doesn't seem important enough to risk backpatching further. Modified Files: -- pgsql/src/backend/access/nbtree: nbtree.c (r1.158 -> r1.159) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/nbtree/nbtree.c?r1=1.158&r2=1.159) nbtutils.c (r1.88 -> r1.89) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/nbtree/nbtutils.c?r1=1.88&r2=1.89) pgsql/src/backend/access/transam: xlog.c (r1.296 -> r1.297) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/transam/xlog.c?r1=1.296&r2=1.297) pgsql/src/backend/commands: dbcommands.c (r1.205 -> r1.206) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/dbcommands.c?r1=1.205&r2=1.206) pgsql/src/backend/port: ipc_test.c (r1.24 -> r1.25) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/port/ipc_test.c?r1=1.24&r2=1.25) pgsql/src/backend/storage/ipc: ipc.c (r1.100 -> r1.101) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/storage/ipc/ipc.c?r1=1.100&r2=1.101) pgsql/src/include/access: nbtree.h (r1.117 -> r1.118) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/access/nbtree.h?r1=1.117&r2=1.118) pgsql/src/include/storage: ipc.h (r1.74 -> r1.75) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/storage/ipc.h?r1=1.74&r2=1.75) pgsql/src/include/utils: elog.h (r1.92 -> r1.93) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/utils/elog.h?r1=1.92&r2=1.93) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Repair two places where SIGTERM exit could leave shared memory
Log Message: --- Repair two places where SIGTERM exit could leave shared memory state corrupted. (Neither is very important if SIGTERM is used to shut down the whole database cluster together, but there's a problem if someone tries to SIGTERM individual backends.) To do this, introduce new infrastructure macros PG_ENSURE_ERROR_CLEANUP/PG_END_ENSURE_ERROR_CLEANUP that take care of transiently pushing an on_shmem_exit cleanup hook. Also use this method for createdb cleanup --- that wasn't a shared-memory-corruption problem, but SIGTERM abort of createdb could leave orphaned files lying around. Backpatch as far as 8.2. The shmem corruption cases don't exist in 8.1, and the createdb usage doesn't seem important enough to risk backpatching further. Tags: REL8_3_STABLE Modified Files: -- pgsql/src/backend/access/nbtree: nbtree.c (r1.156 -> r1.156.2.1) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/nbtree/nbtree.c?r1=1.156&r2=1.156.2.1) nbtutils.c (r1.88 -> r1.88.2.1) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/nbtree/nbtutils.c?r1=1.88&r2=1.88.2.1) pgsql/src/backend/access/transam: xlog.c (r1.292 -> r1.292.2.1) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/transam/xlog.c?r1=1.292&r2=1.292.2.1) pgsql/src/backend/commands: dbcommands.c (r1.204 -> r1.204.2.1) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/dbcommands.c?r1=1.204&r2=1.204.2.1) pgsql/src/backend/port: ipc_test.c (r1.23 -> r1.23.2.1) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/port/ipc_test.c?r1=1.23&r2=1.23.2.1) pgsql/src/backend/storage/ipc: ipc.c (r1.100 -> r1.100.2.1) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/storage/ipc/ipc.c?r1=1.100&r2=1.100.2.1) pgsql/src/include/access: nbtree.h (r1.116 -> r1.116.2.1) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/access/nbtree.h?r1=1.116&r2=1.116.2.1) pgsql/src/include/storage: ipc.h (r1.74 -> r1.74.2.1) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/storage/ipc.h?r1=1.74&r2=1.74.2.1) pgsql/src/include/utils: elog.h (r1.90 -> r1.90.2.1) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/utils/elog.h?r1=1.90&r2=1.90.2.1) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Repair two places where SIGTERM exit could leave shared memory
Log Message: --- Repair two places where SIGTERM exit could leave shared memory state corrupted. (Neither is very important if SIGTERM is used to shut down the whole database cluster together, but there's a problem if someone tries to SIGTERM individual backends.) To do this, introduce new infrastructure macros PG_ENSURE_ERROR_CLEANUP/PG_END_ENSURE_ERROR_CLEANUP that take care of transiently pushing an on_shmem_exit cleanup hook. Also use this method for createdb cleanup --- that wasn't a shared-memory-corruption problem, but SIGTERM abort of createdb could leave orphaned files lying around. Backpatch as far as 8.2. The shmem corruption cases don't exist in 8.1, and the createdb usage doesn't seem important enough to risk backpatching further. Tags: REL8_2_STABLE Modified Files: -- pgsql/src/backend/access/nbtree: nbtree.c (r1.153 -> r1.153.2.1) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/nbtree/nbtree.c?r1=1.153&r2=1.153.2.1) nbtutils.c (r1.79.2.1 -> r1.79.2.2) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/nbtree/nbtutils.c?r1=1.79.2.1&r2=1.79.2.2) pgsql/src/backend/access/transam: xlog.c (r1.258.2.2 -> r1.258.2.3) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/transam/xlog.c?r1=1.258.2.2&r2=1.258.2.3) pgsql/src/backend/commands: dbcommands.c (r1.187.2.2 -> r1.187.2.3) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/dbcommands.c?r1=1.187.2.2&r2=1.187.2.3) pgsql/src/backend/port: ipc_test.c (r1.21 -> r1.21.2.1) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/port/ipc_test.c?r1=1.21&r2=1.21.2.1) pgsql/src/backend/storage/ipc: ipc.c (r1.94 -> r1.94.2.1) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/storage/ipc/ipc.c?r1=1.94&r2=1.94.2.1) pgsql/src/include/access: nbtree.h (r1.106 -> r1.106.2.1) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/access/nbtree.h?r1=1.106&r2=1.106.2.1) pgsql/src/include/storage: ipc.h (r1.72 -> r1.72.2.1) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/storage/ipc.h?r1=1.72&r2=1.72.2.1) pgsql/src/include/utils: elog.h (r1.82 -> r1.82.2.1) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/utils/elog.h?r1=1.82&r2=1.82.2.1) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
