[COMMITTERS] pgsql: Include files copied from libpqport in .gitignore

2014-05-08 Thread Heikki Linnakangas
Include files copied from libpqport in .gitignore Michael Paquier Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/02c9a938057ecb811c65999577d32c5f5e9c99dc Modified Files -- src/interfaces/libpq/.gitignore |2 ++ 1 file changed, 2 insertions(+) -- S

[COMMITTERS] pgsql: Include files copied from libpqport in .gitignore

2014-05-08 Thread Heikki Linnakangas
Include files copied from libpqport in .gitignore Michael Paquier Branch -- REL9_3_STABLE Details --- http://git.postgresql.org/pg/commitdiff/cd7df1060b405c15353e61dfab2404e97c3482c1 Modified Files -- src/interfaces/libpq/.gitignore |1 + 1 file changed, 1 insertion(+)

[COMMITTERS] pgsql: Include files copied from libpqport in .gitignore

2014-05-08 Thread Heikki Linnakangas
Include files copied from libpqport in .gitignore Michael Paquier Branch -- REL9_2_STABLE Details --- http://git.postgresql.org/pg/commitdiff/7603744a077a8f6a878f47e389a3d41844c8adc5 Modified Files -- src/interfaces/libpq/.gitignore |1 + 1 file changed, 1 insertion(+)

[COMMITTERS] pgsql: Include files copied from libpqport in .gitignore

2014-05-08 Thread Heikki Linnakangas
Include files copied from libpqport in .gitignore Michael Paquier Branch -- REL9_1_STABLE Details --- http://git.postgresql.org/pg/commitdiff/5c5bfc0ac3653acad439495c27c78f129668d114 Modified Files -- src/interfaces/libpq/.gitignore |1 + 1 file changed, 1 insertion(+)

[COMMITTERS] pgsql: Protect against torn pages when deleting GIN list pages.

2014-05-08 Thread Heikki Linnakangas
Protect against torn pages when deleting GIN list pages. To-be-deleted list pages contain no useful information, as they are being deleted, but we must still protect the writes from being torn by a crash after a partial write. To do that, re-initialize the pages on WAL replay. Jeff Janes caught t

[COMMITTERS] pgsql: Protect against torn pages when deleting GIN list pages.

2014-05-08 Thread Heikki Linnakangas
Protect against torn pages when deleting GIN list pages. To-be-deleted list pages contain no useful information, as they are being deleted, but we must still protect the writes from being torn by a crash after a partial write. To do that, re-initialize the pages on WAL replay. Jeff Janes caught t

[COMMITTERS] pgsql: Protect against torn pages when deleting GIN list pages.

2014-05-08 Thread Heikki Linnakangas
Protect against torn pages when deleting GIN list pages. To-be-deleted list pages contain no useful information, as they are being deleted, but we must still protect the writes from being torn by a crash after a partial write. To do that, re-initialize the pages on WAL replay. Jeff Janes caught t

[COMMITTERS] pgsql: Protect against torn pages when deleting GIN list pages.

2014-05-08 Thread Heikki Linnakangas
Protect against torn pages when deleting GIN list pages. To-be-deleted list pages contain no useful information, as they are being deleted, but we must still protect the writes from being torn by a crash after a partial write. To do that, re-initialize the pages on WAL replay. Jeff Janes caught t

[COMMITTERS] pgsql: Protect against torn pages when deleting GIN list pages.

2014-05-08 Thread Heikki Linnakangas
Protect against torn pages when deleting GIN list pages. To-be-deleted list pages contain no useful information, as they are being deleted, but we must still protect the writes from being torn by a crash after a partial write. To do that, re-initialize the pages on WAL replay. Jeff Janes caught t

[COMMITTERS] pgsql: Protect against torn pages when deleting GIN list pages.

2014-05-08 Thread Heikki Linnakangas
Protect against torn pages when deleting GIN list pages. To-be-deleted list pages contain no useful information, as they are being deleted, but we must still protect the writes from being torn by a crash after a partial write. To do that, re-initialize the pages on WAL replay. Jeff Janes caught t

[COMMITTERS] pgsql: Allow for platforms that have optreset but not .

2014-05-08 Thread Tom Lane
Allow for platforms that have optreset but not . Reportedly, some versions of mingw are like that, and it seems plausible in general that older platforms might be that way. However, we'd determined experimentally that just doing "extern int" conflicts with the way Cygwin declares these variables,

[COMMITTERS] pgsql: Fix comment.

2014-05-08 Thread Tom Lane
Fix comment. Previous commit was confused about the case we're handling: actually, what the patch is dealing with is platforms that have optreset, *and* have , but the latter fails to declare the former. Because we use a linking probe to set HAVE_INT_OPTRESET, we need to be sure we have a declara

[COMMITTERS] pgsql: Revert "Auto-tune effective_cache size to be 4x shared buffers"

2014-05-08 Thread Tom Lane
Revert "Auto-tune effective_cache size to be 4x shared buffers" This reverts commit ee1e5662d8d8330726eaef7d3110cb7add24d058, as well as a remarkably large number of followup commits, which were mostly concerned with the fact that the implementation didn't work terribly well. It still doesn't: we

[COMMITTERS] pgsql: Increase the default value of effective_cache_size to 4GB.

2014-05-08 Thread Tom Lane
Increase the default value of effective_cache_size to 4GB. Per discussion, the old value of 128MB is ridiculously small on modern machines; in fact, it's not even any larger than the default value of shared_buffers, which it certainly should be. Increase to 4GB, which is unlikely to be any worse

[COMMITTERS] pgsql: Document permissions needed for pg_database_size and pg_tablespa

2014-05-08 Thread Tom Lane
Document permissions needed for pg_database_size and pg_tablespace_size. Back in 8.3, we installed permissions checks in these functions (see commits 8bc225e7990a and cc26599b7206). But we forgot to document that anywhere in the user-facing docs; it did get mentioned in the 8.3 release notes, but

[COMMITTERS] pgsql: Document permissions needed for pg_database_size and pg_tablespa

2014-05-08 Thread Tom Lane
Document permissions needed for pg_database_size and pg_tablespace_size. Back in 8.3, we installed permissions checks in these functions (see commits 8bc225e7990a and cc26599b7206). But we forgot to document that anywhere in the user-facing docs; it did get mentioned in the 8.3 release notes, but

[COMMITTERS] pgsql: Document permissions needed for pg_database_size and pg_tablespa

2014-05-08 Thread Tom Lane
Document permissions needed for pg_database_size and pg_tablespace_size. Back in 8.3, we installed permissions checks in these functions (see commits 8bc225e7990a and cc26599b7206). But we forgot to document that anywhere in the user-facing docs; it did get mentioned in the 8.3 release notes, but

[COMMITTERS] pgsql: Document permissions needed for pg_database_size and pg_tablespa

2014-05-08 Thread Tom Lane
Document permissions needed for pg_database_size and pg_tablespace_size. Back in 8.3, we installed permissions checks in these functions (see commits 8bc225e7990a and cc26599b7206). But we forgot to document that anywhere in the user-facing docs; it did get mentioned in the 8.3 release notes, but

[COMMITTERS] pgsql: Document permissions needed for pg_database_size and pg_tablespa

2014-05-08 Thread Tom Lane
Document permissions needed for pg_database_size and pg_tablespace_size. Back in 8.3, we installed permissions checks in these functions (see commits 8bc225e7990a and cc26599b7206). But we forgot to document that anywhere in the user-facing docs; it did get mentioned in the 8.3 release notes, but

[COMMITTERS] pgsql: Document permissions needed for pg_database_size and pg_tablespa

2014-05-08 Thread Tom Lane
Document permissions needed for pg_database_size and pg_tablespace_size. Back in 8.3, we installed permissions checks in these functions (see commits 8bc225e7990a and cc26599b7206). But we forgot to document that anywhere in the user-facing docs; it did get mentioned in the 8.3 release notes, but

[COMMITTERS] pgsql: Fix missing dependencies in ecpg's test Makefiles.

2014-05-08 Thread Tom Lane
Fix missing dependencies in ecpg's test Makefiles. Ensure that ecpg preprocessor output files are rebuilt when re-testing after a change in the ecpg preprocessor itself, or a change in any of several include files that get copied verbatim into the output files. The lack of these dependencies was w