[COMMITTERS] pgsql: doc: Add event trigger C API documentation

doc: Add event trigger C API documentation From: Dimitri Fontaine Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/0fe21ad8aab03172d4ac2e790479f17edcd3dbbe Modified Files -- doc/src/sgml/event-trigger.sgml | 224 +-- 1

[COMMITTERS] pgsql: doc: Add event trigger C API documentation

doc: Add event trigger C API documentation From: Dimitri Fontaine Branch -- REL9_3_STABLE Details --- http://git.postgresql.org/pg/commitdiff/775a9f3025b16dcc9804cca82e744f41e1523a6e Modified Files -- doc/src/sgml/event-trigger.sgml | 224 ++

[COMMITTERS] pgsql: Install all a Makefile's extension controls, not just the first.

Install all a Makefile's extension controls, not just the first. Bug introduced by commit 6697aa2bc25c83b88d6165340348a31328c35de6 and reported by Robert Haas. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/82b0102650cf85268145a46f0ab488bacf6599a1 Modified Files --

Re: [COMMITTERS] pgsql: Permit super-MaxAllocSize allocations with MemoryContextAllocHug

On Tue, Jul 02, 2013 at 10:33:38AM -0400, Noah Misch wrote: > On Tue, Jul 02, 2013 at 12:08:42PM +0200, Andres Freund wrote: > > On 2013-06-27 19:05:22 +, Noah Misch wrote: > > > Permit super-MaxAllocSize allocations with MemoryContextAllocHuge(). > > > > > > The MaxAllocSize guard is convenie

[COMMITTERS] pgsql: pg_buffercache: document column meanings

pg_buffercache: document column meanings Improve documentation for usagecount and relforknumber. Backpatch to 9.3 Suggestion from Satoshi Nagayasu Branch -- REL9_3_STABLE Details --- http://git.postgresql.org/pg/commitdiff/d3cc1b2ff087cd68f281dad33743640dffbe01d1 Modified Files -

[COMMITTERS] pgsql: Get rid of pg_class.reltoastidxid.

Get rid of pg_class.reltoastidxid. Treat TOAST index just the same as normal one and get the OID of TOAST index from pg_index but not pg_class.reltoastidxid. This change allows us to handle multiple TOAST indexes, and which is required infrastructure for upcoming REINDEX CONCURRENTLY feature. Pat

[COMMITTERS] pgsql: pg_buffercache: document column meanings

pg_buffercache: document column meanings Improve documentation for usagecount and relforknumber. Backpatch to 9.3. Suggestion from Satoshi Nagayasu Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/f71939cd1ac765ba618115f40de4d9c47955a9ef Modified Files --

[COMMITTERS] pgsql: pg_buffercache: document column meanings

pg_buffercache: document column meanings Improve documentation for usagecount and relforknumber. Backpatch to 9.3. Suggestion from Satoshi Nagayasu Branch -- REL9_2_STABLE Details --- http://git.postgresql.org/pg/commitdiff/74414bbd90a307c949489bcc630bdc9559cc5682 Modified Files

[COMMITTERS] pgsql: Revert "Hopefully-portable regression tests for CREATE/ALTER/DRO

Revert "Hopefully-portable regression tests for CREATE/ALTER/DROP COLLATION." This reverts commit 263645305b8f14a3821e04dffa96fa7c1bc2ae86. The buildfarm is sad. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/f33c53ec5b27a90a0f00ac27d4e5178fcc33168f Modified Files

[COMMITTERS] pgsql: Hopefully-portable regression tests for CREATE/ALTER/DROP COLLAT

Hopefully-portable regression tests for CREATE/ALTER/DROP COLLATION. The collate.linux.utf8 test covers some of the same territory, but isn't portable and so probably does not get run often, or on non-Linux platforms. If this approach turns out to be sufficiently portable, we may want to look at

[COMMITTERS] pgsql: Fix handling of auto-updatable views on inherited tables.

Fix handling of auto-updatable views on inherited tables. An INSERT into such a view should work just like an INSERT into its base table, ie the insertion should go directly into that table ... not be duplicated into each child table, as was happening before, per bug #8275 from Rushabh Lathia. On

[COMMITTERS] pgsql: Fix handling of auto-updatable views on inherited tables.

Fix handling of auto-updatable views on inherited tables. An INSERT into such a view should work just like an INSERT into its base table, ie the insertion should go directly into that table ... not be duplicated into each child table, as was happening before, per bug #8275 from Rushabh Lathia. On

[COMMITTERS] pgsql: Unbreak postmaster restart-after-crash sequence

Unbreak postmaster restart-after-crash sequence In patch 82233ce7ea42, AbortStartTime wasn't being reset appropriately after the restart sequence, causing subsequent iterations through ServerLoop to malfunction. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/620935a

[COMMITTERS] pgsql: Regression tests for LISTEN/NOTIFY/UNLISTEN/pg_notify.

Regression tests for LISTEN/NOTIFY/UNLISTEN/pg_notify. Robins Tharakan, reviewed by Szymon Guz Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/00a7767fcc2e4d90e3b4cacb87974ec5a0f32b8c Modified Files -- src/test/regress/expected/async.out | 34 +

[COMMITTERS] pgsql: Additional regression tests for CREATE OPERATOR.

Additional regression tests for CREATE OPERATOR. Robins Tharakan, reviewed by Szymon Guz Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/ada3e776c2a4825ed0387e4bcf335139b101ca98 Modified Files -- src/test/regress/expected/create_operator.out | 142 +

[COMMITTERS] pgsql: Expose object name error fields in PL/pgSQL.

Expose object name error fields in PL/pgSQL. Specifically, permit attaching them to the error in RAISE and retrieving them from a caught error in GET STACKED DIAGNOSTICS. RAISE enforces nothing about the content of the fields; for its purposes, they are just additional string fields. Consequentl

[COMMITTERS] pgsql: Expose object name error fields in PL/pgSQL.

Expose object name error fields in PL/pgSQL. Specifically, permit attaching them to the error in RAISE and retrieving them from a caught error in GET STACKED DIAGNOSTICS. RAISE enforces nothing about the content of the fields; for its purposes, they are just additional string fields. Consequentl