Re: [COMMITTERS] pgsql: Improve performance of timezone loading, especially pg_timezone_

Amit Kapila writes: > On Wed, May 3, 2017 at 7:21 AM, Tom Lane wrote: >> Improve performance of timezone loading, especially pg_timezone_names view. > I am consistently getting below error after this commit in my Win7 machine: > running bootstrap

Re: [COMMITTERS] pgsql: Improve performance of timezone loading, especially pg_timezone_

On Wed, May 3, 2017 at 7:21 AM, Tom Lane wrote: > Improve performance of timezone loading, especially pg_timezone_names view. > I am consistently getting below error after this commit in my Win7 machine: running bootstrap script ... 2017-05-07 05:09:13.383 GMT [7908] LOG:

[COMMITTERS] pgsql: Document current_role.

Document current_role. This system function has been there a very long time, but somehow escaped being listed in func.sgml. Fabien Coelho and Tom Lane Discussion: https://postgr.es/m/alpine.DEB.2.20.1705061027580.3896@lancre Branch -- REL9_4_STABLE Details ---

[COMMITTERS] pgsql: Document current_role.

Document current_role. This system function has been there a very long time, but somehow escaped being listed in func.sgml. Fabien Coelho and Tom Lane Discussion: https://postgr.es/m/alpine.DEB.2.20.1705061027580.3896@lancre Branch -- REL9_3_STABLE Details ---

[COMMITTERS] pgsql: Document current_role.

Document current_role. This system function has been there a very long time, but somehow escaped being listed in func.sgml. Fabien Coelho and Tom Lane Discussion: https://postgr.es/m/alpine.DEB.2.20.1705061027580.3896@lancre Branch -- master Details ---

[COMMITTERS] pgsql: Document current_role.

Document current_role. This system function has been there a very long time, but somehow escaped being listed in func.sgml. Fabien Coelho and Tom Lane Discussion: https://postgr.es/m/alpine.DEB.2.20.1705061027580.3896@lancre Branch -- REL9_2_STABLE Details ---

[COMMITTERS] pgsql: Document current_role.

Document current_role. This system function has been there a very long time, but somehow escaped being listed in func.sgml. Fabien Coelho and Tom Lane Discussion: https://postgr.es/m/alpine.DEB.2.20.1705061027580.3896@lancre Branch -- REL9_5_STABLE Details ---

[COMMITTERS] pgsql: Document current_role.

Document current_role. This system function has been there a very long time, but somehow escaped being listed in func.sgml. Fabien Coelho and Tom Lane Discussion: https://postgr.es/m/alpine.DEB.2.20.1705061027580.3896@lancre Branch -- REL9_6_STABLE Details ---

[COMMITTERS] pgsql: Second pass on 9.6.3 release notes.

Second pass on 9.6.3 release notes. Improve description of logical decoding snapshot issues, per suggestion from Petr Jelinek. Mention possible need to re-sync logical replicas as a post-upgrade task. Minor copy-editing for some other items. Branch -- master Details ---

[COMMITTERS] pgsql: Fix off-by-one possibly leading to skipped XLOG_RUNNING_XACTS re

Fix off-by-one possibly leading to skipped XLOG_RUNNING_XACTS records. Since 6ef2eba3f57f1 ("Skip checkpoints, archiving on idle systems."), GetLastImportantRecPtr() is used to avoid performing superfluous checkpoints, xlog switches, running-xact records when the system is idle. Unfortunately

[COMMITTERS] pgsql: Fix duplicated words in comment.

Fix duplicated words in comment. Reported-By: Peter Geoghegan Discussion: https://postgr.es/m/cah2-wzn3ry2n0gtwndaapd113t+o8l6oz8cm7_f3p8y4awd...@mail.gmail.com Backpatch: no, only present in master Branch -- master Details ---

[COMMITTERS] pgsql: RLS: Fix ALL vs. SELECT+UPDATE policy usage

RLS: Fix ALL vs. SELECT+UPDATE policy usage When we add the SELECT-privilege based policies to the RLS with check options (such as for an UPDATE statement, or when we have INSERT ... RETURNING), we need to be sure and use the 'USING' case if the policy is actually an 'ALL' policy (which could

[COMMITTERS] pgsql: RLS: Fix ALL vs. SELECT+UPDATE policy usage

RLS: Fix ALL vs. SELECT+UPDATE policy usage When we add the SELECT-privilege based policies to the RLS with check options (such as for an UPDATE statement, or when we have INSERT ... RETURNING), we need to be sure and use the 'USING' case if the policy is actually an 'ALL' policy (which could

[COMMITTERS] pgsql: RLS: Fix ALL vs. SELECT+UPDATE policy usage

RLS: Fix ALL vs. SELECT+UPDATE policy usage When we add the SELECT-privilege based policies to the RLS with check options (such as for an UPDATE statement, or when we have INSERT ... RETURNING), we need to be sure and use the 'USING' case if the policy is actually an 'ALL' policy (which could

[COMMITTERS] pgsql: Allow queries submitted by postgres_fdw to be canceled.

Allow queries submitted by postgres_fdw to be canceled. Back-patch of commits f039eaac7131ef2a4cf63a10cf98486f8bcd09d2 and 1b812afb0eafe125b820cc3b95e7ca03821aa675, which arranged (in 9.6+) to make remote queries interruptible. It was known at the time that the same problem existed in the

[COMMITTERS] pgsql: Allow queries submitted by postgres_fdw to be canceled.

Allow queries submitted by postgres_fdw to be canceled. Back-patch of commits f039eaac7131ef2a4cf63a10cf98486f8bcd09d2 and 1b812afb0eafe125b820cc3b95e7ca03821aa675, which arranged (in 9.6+) to make remote queries interruptible. It was known at the time that the same problem existed in the

[COMMITTERS] pgsql: Allow queries submitted by postgres_fdw to be canceled.

Allow queries submitted by postgres_fdw to be canceled. Back-patch of commits f039eaac7131ef2a4cf63a10cf98486f8bcd09d2 and 1b812afb0eafe125b820cc3b95e7ca03821aa675, which arranged (in 9.6+) to make remote queries interruptible. It was known at the time that the same problem existed in the

[COMMITTERS] pgsql: pg_dump: Don't leak memory in buildDefaultACLCommands()

pg_dump: Don't leak memory in buildDefaultACLCommands() buildDefaultACLCommands() didn't destroy the string buffer created in certain cases, leading to a memory leak. Fix by destroying the buffer before returning from the function. Spotted by Coverity. Author: Michael Paquier Back-patch to

[COMMITTERS] pgsql: pg_dump: Don't leak memory in buildDefaultACLCommands()

pg_dump: Don't leak memory in buildDefaultACLCommands() buildDefaultACLCommands() didn't destroy the string buffer created in certain cases, leading to a memory leak. Fix by destroying the buffer before returning from the function. Spotted by Coverity. Author: Michael Paquier Back-patch to

[COMMITTERS] pgsql: doc PG 10: adjustments to BRIN, WAL, JSON, XML items, syntax

doc PG 10: adjustments to BRIN, WAL, JSON, XML items, syntax Reported-by: Alvaro Herrera Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/628462bda908873688ce738a191b470ab769d604 Modified Files -- doc/src/sgml/release-10.sgml | 145