[COMMITTERS] pgsql: Fix function declaration style to respect the coding standard.

Fix function declaration style to respect the coding standard. Branch -- REL9_3_STABLE Details --- http://git.postgresql.org/pg/commitdiff/fc7f6e331d7d35f7f24f72a62e4907887e7bcb11 Modified Files -- contrib/pgbench/pgbench.c |3 +-- 1 file changed, 1 insertion(+), 2 deletio

[COMMITTERS] pgsql: Fix function declaration style to respect the coding standard.

Fix function declaration style to respect the coding standard. Branch -- REL9_4_STABLE Details --- http://git.postgresql.org/pg/commitdiff/9a437994400f5fdadac103fc5df0c5d622d5c8be Modified Files -- contrib/pgbench/pgbench.c |3 +-- 1 file changed, 1 insertion(+), 2 deletio

[COMMITTERS] pgsql: Fix function declaration style to respect the coding standard.

Fix function declaration style to respect the coding standard. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/527e6d3f099df22783465ca7046fc0c8a534c921 Modified Files -- src/bin/pgbench/pgbench.c |3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)

[COMMITTERS] pgsql: Fix comment for GetCurrentIntegerTimestamp().

Fix comment for GetCurrentIntegerTimestamp(). The unit of measure is microseconds, not milliseconds. Backpatch to 9.3 where the function and its comment were added. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/cca8ba9529f8815acd23fe88c32763765d0e1b68 Modified Fi

[COMMITTERS] pgsql: Fix comment for GetCurrentIntegerTimestamp().

Fix comment for GetCurrentIntegerTimestamp(). The unit of measure is microseconds, not milliseconds. Backpatch to 9.3 where the function and its comment were added. Branch -- REL9_3_STABLE Details --- http://git.postgresql.org/pg/commitdiff/f9b38ab6536e0c175cf94bea0c8f2a3d9fed175a Modi

[COMMITTERS] pgsql: Fix comment for GetCurrentIntegerTimestamp().

Fix comment for GetCurrentIntegerTimestamp(). The unit of measure is microseconds, not milliseconds. Backpatch to 9.3 where the function and its comment were added. Branch -- REL9_4_STABLE Details --- http://git.postgresql.org/pg/commitdiff/f9f71503767f0212a1d4141a2370dfc63c7ec050 Modi

[COMMITTERS] pgsql: Don't choke on files that are removed while pg_rewind runs.

Don't choke on files that are removed while pg_rewind runs. If a file is removed from the source server, while pg_rewind is running, the invocation of pg_read_binary_file() will fail. Use the just-added missing_ok option to that function, to have it return NULL instead, and handle that gracefully.

[COMMITTERS] pgsql: Add missing_ok option to the SQL functions for reading files.

Add missing_ok option to the SQL functions for reading files. This makes it possible to use the functions without getting errors, if there is a chance that the file might be removed or renamed concurrently. pg_rewind needs to do just that, although this could be useful for other purposes too. (The

[COMMITTERS] pgsql: Fix double-XLogBeginInsert call in GIN page splits.

Fix double-XLogBeginInsert call in GIN page splits. If data checksums or wal_log_hints is on, and a GIN page is split, the code to find a new, empty, block was called after having already called XLogBeginInsert(). That causes an assertion failure or PANIC, if finding the new block involves updatin

[COMMITTERS] pgsql: Promote the assertion that XLogBeginInsert() is not called twice

Promote the assertion that XLogBeginInsert() is not called twice into ERROR. Seems like cheap insurance for WAL bugs. A spurious call to XLogBeginInsert() in itself would be fairly harmless, but if there is any data registered and the insertion is not completed/cancelled properly, there is a risk

[COMMITTERS] pgsql: Fix markup in docs.

Fix markup in docs. Oops. I could swear I built the docs before pushing, but I guess not.. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/6ab4d38ab085b0177d7ce63f7e1f2fb3f3a8e4a5 Modified Files -- doc/src/sgml/func.sgml |2 +- 1 file changed, 1 inser

[COMMITTERS] pgsql: Also trigger restartpoints based on max_wal_size on standby.

Also trigger restartpoints based on max_wal_size on standby. When archive recovery and restartpoints were initially introduced, checkpoint_segments was ignored on the grounds that the files restored from archive don't consume any space in the recovery server. That was changed in later releases, bu

[COMMITTERS] pgsql: Improve design and implementation of pg_file_settings view.

Improve design and implementation of pg_file_settings view. As first committed, this view reported on the file contents as they were at the last SIGHUP event. That's not as useful as reporting on the current contents, and what's more, it didn't work right on Windows unless the current session had

[COMMITTERS] pgsql: Back-patch some minor bug fixes in GUC code.

Back-patch some minor bug fixes in GUC code. In 9.4, fix a 9.4.1 regression that allowed multiple entries for a PGC_POSTMASTER variable to cause bogus complaints in the postmaster log. (The issue here was that commit bf007a27acd7b2fb unintentionally reverted 3e3f65973a3c94a6, which suppressed any

[COMMITTERS] pgsql: Back-patch some minor bug fixes in GUC code.

Back-patch some minor bug fixes in GUC code. In 9.4, fix a 9.4.1 regression that allowed multiple entries for a PGC_POSTMASTER variable to cause bogus complaints in the postmaster log. (The issue here was that commit bf007a27acd7b2fb unintentionally reverted 3e3f65973a3c94a6, which suppressed any

Re: [COMMITTERS] pgsql: Fix the fallback memory barrier implementation to be reentrant.

Andres Freund writes: > Fix the fallback memory barrier implementation to be reentrant. Seems this has not done the trick: anole just crashed with "stuck spinlock" again. regards, tom lane -- Sent via pgsql-committers mailing list ([email protected]) To m

[COMMITTERS] pgsql: Run the C portions of guc-file.l through pgindent.

Run the C portions of guc-file.l through pgindent. Yeah, I know, pretty anal-retentive of me. But we oughta find some way to automate this for the .y and .l files. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/2bdc51a2946f9a66688eb705cd0cb584ebd8240a Modified Fil

Re: [COMMITTERS] pgsql: Run the C portions of guc-file.l through pgindent.

On Mon, Jun 29, 2015 at 9:49 AM, Tom Lane wrote: > Run the C portions of guc-file.l through pgindent. > > Yeah, I know, pretty anal-retentive of me. But we oughta find some > way to automate this for the .y and .l files. .y files may be tricky and .l files less. Still one good way to test such t

[COMMITTERS] pgsql: Translation updates

Translation updates Source-Git-URL: git://git.postgresql.org/git/pgtranslation/messages.git Source-Git-Hash: fb7e72f46cfafa1b5bfe4564d9686d63a1e6383f Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/c5e5d444de85a7caff462443c5915544d4406a62 Modified Files