Re: [COMMITTERS] pgsql: Introduce replication slots.

2014-02-25 Thread Thom Brown
On 6 February 2014 10:29, Andres Freund wrote: > Hi Fujii, > > On 2014-02-01 16:47:47 +0900, Fujii Masao wrote: > > This patch changed basebackup.c so that it skips pg_replslot. It's OK > > to skip all files in that directory, but an empty pg_replslot must be > > included in the backup. Otherwise

Re: [COMMITTERS] pgsql: Introduce replication slots.

2014-02-25 Thread Robert Haas
On Tue, Feb 25, 2014 at 10:11 AM, Thom Brown wrote: > On 6 February 2014 10:29, Andres Freund wrote: >> Hi Fujii, >> >> On 2014-02-01 16:47:47 +0900, Fujii Masao wrote: >> > This patch changed basebackup.c so that it skips pg_replslot. It's OK >> > to skip all files in that directory, but an empt

[COMMITTERS] pgsql: pg_basebackup: Skip only the *contents* of pg_replslot.

2014-02-25 Thread Robert Haas
pg_basebackup: Skip only the *contents* of pg_replslot. Include the directory itself. Fujii Masao Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/278c94209b90b8e241f64ea4ce2d955b63b1f5d7 Modified Files -- src/backend/replication/basebackup.c | 16

[COMMITTERS] pgsql: Show xid and xmin in pg_stat_activity and pg_stat_replication.

2014-02-25 Thread Robert Haas
Show xid and xmin in pg_stat_activity and pg_stat_replication. Christian Kruse, reviewed by Andres Freund and myself, with further minor adjustments by me. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/dd1a3bccca241a998b4ebf39d67202698e5fa599 Modified Files --

[COMMITTERS] pgsql: Update a few comments to mention materialized views.

2014-02-25 Thread Robert Haas
Update a few comments to mention materialized views. Etsuro Fujita Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/cf6aa68bbd78e3119d5156616b474fea47e10a33 Modified Files -- src/backend/commands/tablecmds.c | 13 - 1 file changed, 8 insertio

[COMMITTERS] pgsql: Use SnapshotDirty rather than an active snapshot to probe index

2014-02-25 Thread Tom Lane
Use SnapshotDirty rather than an active snapshot to probe index endpoints. If there are lots of uncommitted tuples at the end of the index range, get_actual_variable_range() ends up fetching each one and doing an MVCC visibility check on it, until it finally hits a visible tuple. This is bad enou

[COMMITTERS] pgsql: Use SnapshotDirty rather than an active snapshot to probe index

2014-02-25 Thread Tom Lane
Use SnapshotDirty rather than an active snapshot to probe index endpoints. If there are lots of uncommitted tuples at the end of the index range, get_actual_variable_range() ends up fetching each one and doing an MVCC visibility check on it, until it finally hits a visible tuple. This is bad enou

[COMMITTERS] pgsql: Use SnapshotDirty rather than an active snapshot to probe index

2014-02-25 Thread Tom Lane
Use SnapshotDirty rather than an active snapshot to probe index endpoints. If there are lots of uncommitted tuples at the end of the index range, get_actual_variable_range() ends up fetching each one and doing an MVCC visibility check on it, until it finally hits a visible tuple. This is bad enou

[COMMITTERS] pgsql: Use SnapshotDirty rather than an active snapshot to probe index

2014-02-25 Thread Tom Lane
Use SnapshotDirty rather than an active snapshot to probe index endpoints. If there are lots of uncommitted tuples at the end of the index range, get_actual_variable_range() ends up fetching each one and doing an MVCC visibility check on it, until it finally hits a visible tuple. This is bad enou

[COMMITTERS] pgsql: Use SnapshotDirty rather than an active snapshot to probe index

2014-02-25 Thread Tom Lane
Use SnapshotDirty rather than an active snapshot to probe index endpoints. If there are lots of uncommitted tuples at the end of the index range, get_actual_variable_range() ends up fetching each one and doing an MVCC visibility check on it, until it finally hits a visible tuple. This is bad enou