[COMMITTERS] pgsql: Teach pgrowlocks to check relkind before scanning

Teach pgrowlocks to check relkind before scanning Author: Amit Langote Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/b56818abd450a87e2e3cb03b2cf3eede73487926 Modified Files -- contrib/pgrowlocks/pgrowlocks.c | 14

[COMMITTERS] pgsql: Fix possibility of creating a "phantom" segment after promotion.

Fix possibility of creating a "phantom" segment after promotion. When promoting a standby just after a XLOG_SWITCH record was replayed, and next segment(s) are already are locally available (via walsender, restore_command + trigger/recovery target), that segment could accidentally be recycled

[COMMITTERS] pgsql: Fix possibility of creating a "phantom" segment after promotion.

Fix possibility of creating a "phantom" segment after promotion. When promoting a standby just after a XLOG_SWITCH record was replayed, and next segment(s) are already are locally available (via walsender, restore_command + trigger/recovery target), that segment could accidentally be recycled

[COMMITTERS] pgsql: Fix possibility of creating a "phantom" segment after promotion.

Fix possibility of creating a "phantom" segment after promotion. When promoting a standby just after a XLOG_SWITCH record was replayed, and next segment(s) are already are locally available (via walsender, restore_command + trigger/recovery target), that segment could accidentally be recycled

[COMMITTERS] pgsql: Fix possibility of creating a "phantom" segment after promotion.

Fix possibility of creating a "phantom" segment after promotion. When promoting a standby just after a XLOG_SWITCH record was replayed, and next segment(s) are already are locally available (via walsender, restore_command + trigger/recovery target), that segment could accidentally be recycled

[COMMITTERS] pgsql: Fix possibility of creating a "phantom" segment after promotion.

Fix possibility of creating a "phantom" segment after promotion. When promoting a standby just after a XLOG_SWITCH record was replayed, and next segment(s) are already are locally available (via walsender, restore_command + trigger/recovery target), that segment could accidentally be recycled

[COMMITTERS] pgsql: Fix possibility of creating a "phantom" segment after promotion.

Fix possibility of creating a "phantom" segment after promotion. When promoting a standby just after a XLOG_SWITCH record was replayed, and next segment(s) are already are locally available (via walsender, restore_command + trigger/recovery target), that segment could accidentally be recycled

Re: [COMMITTERS] pgsql: Adjust pgindent script to use pg_bsd_indent 2.0.

On Wed, Jun 21, 2017 at 06:26:29PM +, Tom Lane wrote: > Adjust pgindent script to use pg_bsd_indent 2.0. > > Update version-checking code and list of switches. Delete obsolete > quasi-support for using GNU indent. Remove a lot of no-longer-needed > workarounds for bugs of the old version,

[COMMITTERS] pgsql: Manually un-break a few URLs that pgindent used to insist on spl

Manually un-break a few URLs that pgindent used to insist on splitting. These will no longer get re-split by pgindent runs, so it's worth cleaning them up now. Discussion: https://postgr.es/m/e1damxk-0006ee...@gemulon.postgresql.org Discussion: https://postgr.es/m/30527.1495162...@sss.pgh.pa.us

[COMMITTERS] pgsql: Remove entab and associated detritus.

Remove entab and associated detritus. We don't need this anymore, because pg_bsd_indent has been taught to follow the same tab-vs-space rules that entab used to enforce. Discussion: https://postgr.es/m/e1damxk-0006ee...@gemulon.postgresql.org Discussion:

[COMMITTERS] pgsql: Reformat comments about ResultRelInfo

Reformat comments about ResultRelInfo Also add a comment on its new member PartitionRoot. Reported-by: Etsuro Fujita Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/113b0045e20d40f726a0a30e33214455e4f1385e Modified Files

[COMMITTERS] pgsql: Phase 3 of pgindent updates.

Phase 3 of pgindent updates. Don't move parenthesized lines to the left, even if that means they flow past the right margin. By default, BSD indent lines up statement continuation lines that are within parentheses so that they start just to the right of the preceding left parenthesis. However,

[COMMITTERS] pgsql: Restart logical replication launcher when killed

Restart logical replication launcher when killed Author: Yugo Nagata Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/f669c09989bda894d6ba01634ccb229f0687c08a Modified Files -- src/backend/tcop/postgres.c | 5 +++-- 1 file changed,

[COMMITTERS] pgsql: Initial pgindent run with pg_bsd_indent version 2.0.

Initial pgindent run with pg_bsd_indent version 2.0. The new indent version includes numerous fixes thanks to Piotr Stefaniak. The main changes visible in this commit are: * Nicer formatting of function-pointer declarations. * No longer unexpectedly removes spaces in expressions using casts,

[COMMITTERS] pgsql: Adjust pgindent script to use pg_bsd_indent 2.0.

Adjust pgindent script to use pg_bsd_indent 2.0. Update version-checking code and list of switches. Delete obsolete quasi-support for using GNU indent. Remove a lot of no-longer-needed workarounds for bugs of the old version, and improve comments for the hacks that remain. Update run_build()

[COMMITTERS] pgsql: Final pgindent run with old pg_bsd_indent (version 1.3).

Final pgindent run with old pg_bsd_indent (version 1.3). This is just to have a clean basis for comparison with the results of the new version (which will indeed end up reverting some of these changes...) Discussion: https://postgr.es/m/e1damxk-0006ee...@gemulon.postgresql.org Discussion:

[COMMITTERS] pgsql: Prevent table partitions from being turned into views.

Prevent table partitions from being turned into views. A table partition must be a table, not a view, so don't allow a "_RETURN" rule to be added that would convert an existing table partition into a view. Amit Langote Discussion:

[COMMITTERS] pgsql: Fix typo in comment.

Fix typo in comment. Etsuro Fujita Branch -- REL9_6_STABLE Details --- https://git.postgresql.org/pg/commitdiff/6fd9930e68a3de6a05e6f60b08b16f219982ad05 Modified Files -- src/backend/executor/execMain.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) -- Sent via

[COMMITTERS] pgsql: Fix typo in comment.

Fix typo in comment. Etsuro Fujita Branch -- REL9_5_STABLE Details --- https://git.postgresql.org/pg/commitdiff/26bef29fdd4cf754ebdf0157858b776abe90932c Modified Files -- src/backend/executor/execMain.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) -- Sent via

[COMMITTERS] pgsql: Fix typo in comment.

Fix typo in comment. Etsuro Fujita Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/ba1f017069dd87d309e2716bf08a40df42b29baa Modified Files -- src/backend/executor/execMain.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) -- Sent via