[COMMITTERS] pgsql: set_stack_base() no longer needs to be called in PostgresMain.

set_stack_base() no longer needs to be called in PostgresMain. This was a thinko in previous commit. Now that stack base pointer is now set in PostmasterMain and SubPostmasterMain, it doesn't need to be set in PostgresMain anymore. Branch -- REL9_1_STABLE Details --- http://git.postgresq

[COMMITTERS] pgsql: set_stack_base() no longer needs to be called in PostgresMain.

set_stack_base() no longer needs to be called in PostgresMain. This was a thinko in previous commit. Now that stack base pointer is now set in PostmasterMain and SubPostmasterMain, it doesn't need to be set in PostgresMain anymore. Branch -- REL8_3_STABLE Details --- http://git.postgresq

[COMMITTERS] pgsql: set_stack_base() no longer needs to be called in PostgresMain.

set_stack_base() no longer needs to be called in PostgresMain. This was a thinko in previous commit. Now that stack base pointer is now set in PostmasterMain and SubPostmasterMain, it doesn't need to be set in PostgresMain anymore. Branch -- master Details --- http://git.postgresql.org/p

[COMMITTERS] pgsql: set_stack_base() no longer needs to be called in PostgresMain.

set_stack_base() no longer needs to be called in PostgresMain. This was a thinko in previous commit. Now that stack base pointer is now set in PostmasterMain and SubPostmasterMain, it doesn't need to be set in PostgresMain anymore. Branch -- REL8_4_STABLE Details --- http://git.postgresq

[COMMITTERS] pgsql: Do stack-depth checking in all postmaster children.

Do stack-depth checking in all postmaster children. We used to only initialize the stack base pointer when starting up a regular backend, not in other processes. In particular, autovacuum workers can run arbitrary user code, and without stack-depth checking, infinite recursion in e.g an index expr

[COMMITTERS] pgsql: Do stack-depth checking in all postmaster children.

Do stack-depth checking in all postmaster children. We used to only initialize the stack base pointer when starting up a regular backend, not in other processes. In particular, autovacuum workers can run arbitrary user code, and without stack-depth checking, infinite recursion in e.g an index expr

[COMMITTERS] pgsql: set_stack_base() no longer needs to be called in PostgresMain.

set_stack_base() no longer needs to be called in PostgresMain. This was a thinko in previous commit. Now that stack base pointer is now set in PostmasterMain and SubPostmasterMain, it doesn't need to be set in PostgresMain anymore. Branch -- REL9_0_STABLE Details --- http://git.postgresq

[COMMITTERS] pgsql: Do stack-depth checking in all postmaster children.

Do stack-depth checking in all postmaster children. We used to only initialize the stack base pointer when starting up a regular backend, not in other processes. In particular, autovacuum workers can run arbitrary user code, and without stack-depth checking, infinite recursion in e.g an index expr

[COMMITTERS] pgsql: Do stack-depth checking in all postmaster children.

Do stack-depth checking in all postmaster children. We used to only initialize the stack base pointer when starting up a regular backend, not in other processes. In particular, autovacuum workers can run arbitrary user code, and without stack-depth checking, infinite recursion in e.g an index expr

[COMMITTERS] pgsql: Do stack-depth checking in all postmaster children.

Do stack-depth checking in all postmaster children. We used to only initialize the stack base pointer when starting up a regular backend, not in other processes. In particular, autovacuum workers can run arbitrary user code, and without stack-depth checking, infinite recursion in e.g an index expr

[COMMITTERS] pgsql: Improve management of "sticky" entries in contrib/pg_stat_statem

Improve management of "sticky" entries in contrib/pg_stat_statements. This patch addresses a deficiency in the previous pg_stat_statements patch. We want to give sticky entries an initial "usage" factor high enough that they probably will stick around until their query is completed. However, if t

[COMMITTERS] pgsql: Teach SLRU code to avoid replacing I/O-busy pages.

Teach SLRU code to avoid replacing I/O-busy pages. Patch by me; review by Tom Lane and others. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/3ae5133b1cf478d51f2003bc68ba0edb84c7 Modified Files -- src/backend/access/transam/slru.c | 92 +++

[COMMITTERS] pgsql: Remove link to ODBCng project from the docs.

Remove link to ODBCng project from the docs. Thom Browne pointed out that the URL was out of date, and Devrim GÜNDÜZ pointed out that the project isn't maintained anymore. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/140a4fbf1a87891a79a2c61a08416828d39f286a Modif