[DOCS] Link section in custom scan documentation

Hi, I propose attached which does: the BeginCustomScan callback will be invoked to give the -custom scan provider a chance to do whatever else is needed. +custom scan provider a chance to do whatever else is needed. See +for more details. It would be similar to how it's done els

[DOCS] Typo in ddl.sgml

Hi, s/inheiritance/inheritance/g Thanks, Amit typo-ddl-sgml.patch Description: Binary data -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs

[DOCS] Typo in mvcc.sgml

Hi, Attached fixes a typo in mvcc.sgml - Read and explicit locking.on the master. + Read and explicit locking on the master. Thanks, Amit mvcc-doc-typo.patch Description: Binary data -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscriptio

[DOCS] Typo fix in doc/src/sgml/test-shm-mq.sgml

Hi, Attached fixes a minor typo on test_shm_mq doc page s/"has been send"/"has been sent" -- Amit test-shm-mq-typo-fix.patch Description: Binary data -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql

Re: [DOCS] Typo in doc/src/sgml/monitoring.sgml? s/tranche/trance?

On Wed, Apr 23, 2014 at 6:15 PM, Amit Langote wrote: > Hi, > > Attached fixes a typo in doc/src/sgml/monitoring.sgml. > Sorry, typo in subject (kinda ironic!); I meant "s/trance/tranche?" Patch attached again. -- Amit docs-monitoring-lwlock-tranche-not-trance-fix.pat

[DOCS] Typo in doc/src/sgml/monitoring.sgml? s/tranche/trance?

Hi, Attached fixes a typo in doc/src/sgml/monitoring.sgml. -- Amit docs-monitoring-lwlock-tranche-not-trance-fix.patch Description: Binary data -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs

[DOCS] [doc] EXPLAIN CREATE MATERIALIZED VIEW AS?

Hi, Attached adds CREATE MATERIALIZED VIEW AS to the list of statements that can be EXPLAINed. -- Amit explain-create-materialized-view-as.patch Description: Binary data -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql

Re: [DOCS] [GENERAL] About upgrading a (tuple?) lock in a rollback'd sub-transaction

On Fri, Apr 11, 2014 at 11:52 AM, Alvaro Herrera wrote: > Amit Langote wrote: >> On Thu, Apr 10, 2014 at 10:25 PM, Rob Sargent wrote: >> > And it also tells you how to stop it --bibtex iirc >> >> Yeah, it's a caution against a potentially harmful usage anyway

Re: [DOCS] [GENERAL] About upgrading a (tuple?) lock in a rollback'd sub-transaction

On Thu, Apr 10, 2014 at 10:25 PM, Rob Sargent wrote: > And it also tells you how to stop it --bibtex iirc > Yeah, it's a caution against a potentially harmful usage anyway. Users should not use it at all. I was just wondering if the description of the behavior, that is, potential disappearance o

[DOCS] About upgrading a (tuple?) lock in a rollback'd sub-transaction

Hi, Currently there is a warning against the following in manual: BEGIN; SELECT * FROM mytable WHERE key = 1 FOR UPDATE; SAVEPOINT s; UPDATE mytable SET ... WHERE key = 1; ROLLBACK TO s; here: http://www.postgresql.org/docs/9.2/static/sql-select.html IIUC, it says if the lock-upgrading sub-tran

Re: [DOCS] Fwd: [GENERAL] Table Rewrite During ALTER TABLE ... ADD COLUMN ... DEFAULT NULL

On Fri, Apr 4, 2014 at 1:46 AM, Tom Lane wrote: > Amit Langote writes: >> On Thu, Apr 3, 2014 at 1:19 PM, Tom Lane wrote: >>> We could just rephrase the ALTER TABLE docs to say that the table >>> rewrite is avoided if you omit the DEFAULT clause, rather than >>&

[DOCS] Fwd: [GENERAL] Table Rewrite During ALTER TABLE ... ADD COLUMN ... DEFAULT NULL

-- Forwarded message -- From: Amit Langote Date: Thu, Apr 3, 2014 at 1:53 PM Subject: Re: [GENERAL] Table Rewrite During ALTER TABLE ... ADD COLUMN ... DEFAULT NULL To: Tom Lane Cc: Postgres General On Thu, Apr 3, 2014 at 1:19 PM, Tom Lane wrote: > Amit Langote writes: &g