pgsql: psql: Add option for procedures to \df

psql: Add option for procedures to \df Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/fb421231daaa5228542ef6644cdee505fbc31dba Modified Files -- doc/src/sgml/ref/psql-ref.sgml | 6 ++-- src/bin/psql/command.c | 1

pgsql: psql: Add option for procedures to \df

psql: Add option for procedures to \df Branch -- REL_11_STABLE Details --- https://git.postgresql.org/pg/commitdiff/07055a2c8cbfb772d3c7c114cfe12dddae0f90fe Modified Files -- doc/src/sgml/ref/psql-ref.sgml | 6 ++-- src/bin/psql/command.c

Re: pgsql: Hand code string to integer conversion for performance.

On 23 July 2018 at 10:30, Andres Freund wrote: > Hand code string to integer conversion for performance. This could do with the attached to silence the compiler warnings from compilers that don't understand ereport(ERROR) does not return. -- David Rowley http://www.2ndQuadran

pgsql: Defend against some potential spurious compiler warnings in 86ea

Defend against some potential spurious compiler warnings in 86eaf208e. Author: David Rowley Discussion: https://postgr.es/m/cakjs1f-abcfefu92gzzyqnovrnptuwczsymr2nhcyf9uhun...@mail.gmail.com Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/b2bb3dc0e0d9825640654b9ae0

Re: pgsql: Hand code string to integer conversion for performance.

On 2018-07-24 22:10:09 +1200, David Rowley wrote: > On 23 July 2018 at 10:30, Andres Freund wrote: > > Hand code string to integer conversion for performance. > > This could do with the attached to silence the compiler warnings from > compilers that don't understand ereport(ERROR) does not return

pgsql: doc: Fix reference to "decoder" to instead be the correct "outpu

doc: Fix reference to "decoder" to instead be the correct "output plugin". Author: Jonathan Katz Discussion: https://postgr.es/m/[email protected] Backpatch: 9.4-, where logical decoding was added Branch -- REL9_6_STABLE Details --- https://git.postgres

pgsql: doc: Fix reference to "decoder" to instead be the correct "outpu

doc: Fix reference to "decoder" to instead be the correct "output plugin". Author: Jonathan Katz Discussion: https://postgr.es/m/[email protected] Backpatch: 9.4-, where logical decoding was added Branch -- REL_11_STABLE Details --- https://git.postgres

pgsql: doc: Fix reference to "decoder" to instead be the correct "outpu

doc: Fix reference to "decoder" to instead be the correct "output plugin". Author: Jonathan Katz Discussion: https://postgr.es/m/[email protected] Backpatch: 9.4-, where logical decoding was added Branch -- master Details --- https://git.postgresql.org/

pgsql: doc: Fix reference to "decoder" to instead be the correct "outpu

doc: Fix reference to "decoder" to instead be the correct "output plugin". Author: Jonathan Katz Discussion: https://postgr.es/m/[email protected] Backpatch: 9.4-, where logical decoding was added Branch -- REL_10_STABLE Details --- https://git.postgres

pgsql: doc: Fix reference to "decoder" to instead be the correct "outpu

doc: Fix reference to "decoder" to instead be the correct "output plugin". Author: Jonathan Katz Discussion: https://postgr.es/m/[email protected] Backpatch: 9.4-, where logical decoding was added Branch -- REL9_5_STABLE Details --- https://git.postgres

pgsql: doc: Fix reference to "decoder" to instead be the correct "outpu

doc: Fix reference to "decoder" to instead be the correct "output plugin". Author: Jonathan Katz Discussion: https://postgr.es/m/[email protected] Backpatch: 9.4-, where logical decoding was added Branch -- REL9_4_STABLE Details --- https://git.postgres

Re: pgsql: Hand code string to integer conversion for performance.

On 25 July 2018 at 05:11, Andres Freund wrote: > Pushed. Not sure if any of those do enough control flow analysis to > even consider those blocks reachable? But anyway, doesn't hurt. Thanks. MSVC was producing a warning. -- David Rowley http://www.2ndQuadrant.com/ PostgreS

pgsql: Pad semaphores to avoid false sharing.

Pad semaphores to avoid false sharing. In a USE_UNNAMED_SEMAPHORES build, the default on Linux and FreeBSD since commit ecb0d20a, we have an array of sem_t objects. This turned out to reduce performance compared to the previous default USE_SYSV_SEMAPHORES on an 8 socket system. Testing showed th

pgsql: Pad semaphores to avoid false sharing.

Pad semaphores to avoid false sharing. In a USE_UNNAMED_SEMAPHORES build, the default on Linux and FreeBSD since commit ecb0d20a, we have an array of sem_t objects. This turned out to reduce performance compared to the previous default USE_SYSV_SEMAPHORES on an 8 socket system. Testing showed th

pgsql: Pad semaphores to avoid false sharing.

Pad semaphores to avoid false sharing. In a USE_UNNAMED_SEMAPHORES build, the default on Linux and FreeBSD since commit ecb0d20a, we have an array of sem_t objects. This turned out to reduce performance compared to the previous default USE_SYSV_SEMAPHORES on an 8 socket system. Testing showed th

pgsql: Add strict_multi_assignment and too_many_rows plpgsql checks

Add strict_multi_assignment and too_many_rows plpgsql checks Until now shadowed_variables was the only plpgsql check supported by plpgsql.extra_warnings and plpgsql.extra_errors. This patch introduces two new checks - strict_multi_assignment and too_many_rows. Unlike shadowed_variables, these ne