[COMMITTERS] pgsql: Make SyncRepWakeQueue to a static function

Make SyncRepWakeQueue to a static function It is only used in src/backend/replication/syncrep.c. Back-patch to all supported branches except 9.1 which declares the function as static. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/656ea810e5ebc4d741275b37310a32

[COMMITTERS] pgsql: Make SyncRepWakeQueue to a static function

Make SyncRepWakeQueue to a static function It is only used in src/backend/replication/syncrep.c. Back-patch to all supported branches except 9.1 which declares the function as static. Branch -- REL9_4_STABLE Details --- http://git.postgresql.org/pg/commitdiff/3740bb8347a946232ad28117439

[COMMITTERS] pgsql: Make SyncRepWakeQueue to a static function

Make SyncRepWakeQueue to a static function It is only used in src/backend/replication/syncrep.c. Back-patch to all supported branches except 9.1 which declares the function as static. Branch -- REL9_3_STABLE Details --- http://git.postgresql.org/pg/commitdiff/56abebb9be6d1e7179d10cdc362

[COMMITTERS] pgsql: Make SyncRepWakeQueue to a static function

Make SyncRepWakeQueue to a static function It is only used in src/backend/replication/syncrep.c. Back-patch to all supported branches except 9.1 which declares the function as static. Branch -- REL9_2_STABLE Details --- http://git.postgresql.org/pg/commitdiff/e37c1090df88ca6d7e88f3753fa

[COMMITTERS] pgsql: Add an ASSERT statement in plpgsql.

Add an ASSERT statement in plpgsql. This is meant to make it easier to insert simple debugging cross-checks in plpgsql functions. Pavel Stehule, reviewed by Jim Nasby Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/a4847fc3ef139ba9a8ffebb6ffa06ee72078ffa2 Modified

[COMMITTERS] pgsql: Centralize definition of integer limits.

Centralize definition of integer limits. Several submitted and even committed patches have run into the problem that C89, our baseline, does not provide minimum/maximum values for various integer datatypes. C99's stdint.h does, but we can't rely on it. Several parts of the code defined limits loc

[COMMITTERS] pgsql: Return ObjectAddress in many ALTER TABLE sub-routines

Return ObjectAddress in many ALTER TABLE sub-routines Since commit a2e35b53c39b2a, most CREATE and ALTER commands return the ObjectAddress of the affected object. This is useful for event triggers to try to figure out exactly what happened. This patch extends this idea a bit further to cover ALT

[COMMITTERS] pgsql: Upgrade src/port/rint.c to be POSIX-compliant.

Upgrade src/port/rint.c to be POSIX-compliant. The POSIX spec says that rint() rounds halfway cases to nearest even. Our substitute implementation failed to do that, rather rounding halfway cases away from zero; and it also got some other cases (such as minus zero) wrong. This led to observable c

[COMMITTERS] pgsql: Reduce pinning and buffer content locking for btree scans.

Reduce pinning and buffer content locking for btree scans. Even though the main benefit of the Lehman and Yao algorithm for btrees is that no locks need be held between page reads in an index search, we were holding a buffer pin on each leaf page after it was read until we were ready to read the n

[COMMITTERS] pgsql: Add OID output argument to DefineTSConfiguration

Add OID output argument to DefineTSConfiguration ... which is set to the OID of a copied text search config, whenever the COPY clause is used. This is in the spirit of commit a2e35b53c39. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/8217fb1441ce4b4e1785f9acfa0ce5

[COMMITTERS] pgsql: Fix bug for array-formatted identities of user mappings

Fix bug for array-formatted identities of user mappings I failed to realize that server names reported in the object args array would get quoted, which is wrong; remove that, making sure that it's only quoted in the string-formatted identity. This bug was introduced by my commit cf34e373, which w

[COMMITTERS] pgsql: Fix gram.y comment to match reality

Fix gram.y comment to match reality There are other comments in there that don't precisely match what's implemented, but this one confused me enough to be worth fixing. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/dc8e05295ab126bc4c943cab3e8e117489ecb246 Modified

Re: [COMMITTERS] pgsql: Allow empty target list in SELECT.

On 25 March 2015 at 01:04, Bruce Momjian wrote: > On Fri, Mar 20, 2015 at 08:25:50AM -0400, Bruce Momjian wrote: > > > regression=# create table foo(); > > > CREATE TABLE > > > regression=# insert into foo default values; > > > INSERT 0 1 > > > regression=# insert into foo default values; > > > I