On 8 May 2015 at 04:43, Andres Freund and...@anarazel.de wrote:
Add support for INSERT ... ON CONFLICT DO NOTHING/UPDATE.
The newly added ON CONFLICT clause allows to specify an alternative to
raising a unique or exclusion constraint violation error when inserting.
ON CONFLICT refers to
Even when autovacuum=off, force it for members as we do in other cases.
Thomas Munro, with some adjustments by me.
Branch
--
REL9_3_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/543fbecee5c182528fc1ecee44d7e4e981801c0b
Modified Files
--
Even when autovacuum=off, force it for members as we do in other cases.
Thomas Munro, with some adjustments by me.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/04e6d3b877e060d8445eb653b7ea26b1ee5cec6b
Modified Files
--
Even when autovacuum=off, force it for members as we do in other cases.
Thomas Munro, with some adjustments by me.
Branch
--
REL9_4_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/8ec1a3a541f66bed8deea0ab7b0b11687f1a0a8f
Modified Files
--
pg_dump: suppress Tablespace: comment for default tablespaces
Report by Hans Ginzel
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/c71e273402bbb4262a3d09f045880d485076cd40
Modified Files
--
src/bin/pg_dump/pg_backup_archiver.c |2 +-
1 file
Allow on-the-fly capture of DDL event details
This feature lets user code inspect and take action on DDL events.
Whenever a ddl_command_end event trigger is installed, DDL actions
executed are saved to a list which can be inspected during execution of
a function attached to ddl_command_end.
The
Allow LOCK TABLE .. ROW EXCLUSIVE MODE with INSERT
INSERT acquires RowExclusiveLock during normal operation and therefore
it makes sense to allow LOCK TABLE .. ROW EXCLUSIVE MODE to be executed
by users who have INSERT rights on a table (even if they don't have
UPDATE or DELETE).
Not
Replace some appendStringInfo* calls with more appropriate variants
Author: David Rowley dgrowle...@gmail.com
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/d02f16470f117db3038dbfd87662d5f0eb5a2a9b
Modified Files
--
contrib/postgres_fdw/postgres_fdw.c
On Tue, May 12, 2015 at 11:43 AM, Michael Paquier
michael.paqu...@gmail.com wrote:
On Tue, May 12, 2015 at 11:37 AM, Alvaro Herrera
alvhe...@2ndquadrant.com wrote:
Michael Paquier wrote:
On Tue, May 12, 2015 at 7:16 AM, Alvaro Herrera alvhe...@alvh.no-ip.org
wrote:
Not sure what's the real
Michael Paquier wrote:
On Tue, May 12, 2015 at 11:43 AM, Michael Paquier
michael.paqu...@gmail.com wrote:
On Tue, May 12, 2015 at 11:37 AM, Alvaro Herrera
alvhe...@2ndquadrant.com wrote:
Michael Paquier wrote:
On Tue, May 12, 2015 at 7:16 AM, Alvaro Herrera alvhe...@alvh.no-ip.org
On Tue, May 12, 2015 at 1:05 PM, Alvaro Herrera
alvhe...@2ndquadrant.com wrote:
Michael Paquier wrote:
On Tue, May 12, 2015 at 11:43 AM, Michael Paquier
michael.paqu...@gmail.com wrote:
On Tue, May 12, 2015 at 11:37 AM, Alvaro Herrera
alvhe...@2ndquadrant.com wrote:
Michael Paquier wrote:
On Tue, May 12, 2015 at 1:18 PM, Michael Paquier
michael.paqu...@gmail.com wrote:
On Tue, May 12, 2015 at 1:05 PM, Alvaro Herrera
alvhe...@2ndquadrant.com wrote:
Michael Paquier wrote:
On Tue, May 12, 2015 at 11:43 AM, Michael Paquier
michael.paqu...@gmail.com wrote:
On Tue, May 12, 2015 at
On Tue, May 12, 2015 at 7:16 AM, Alvaro Herrera alvhe...@alvh.no-ip.org wrote:
Allow on-the-fly capture of DDL event details
This feature lets user code inspect and take action on DDL events.
Whenever a ddl_command_end event trigger is installed, DDL actions
executed are saved to a list which
On Mon, May 11, 2015 at 1:49 AM, Thom Brown t...@linux.com wrote:
I haven't had time for a proper read of this patch, but I did
immediately notice this:
HINT: For example, ON CONFLICT ON CONFLICT (column).
This should perhaps either be:
HINT: For example, ON CONFLICT (column).
or
Michael Paquier wrote:
On Tue, May 12, 2015 at 7:16 AM, Alvaro Herrera alvhe...@alvh.no-ip.org
wrote:
Allow on-the-fly capture of DDL event details
This feature lets user code inspect and take action on DDL events.
Whenever a ddl_command_end event trigger is installed, DDL actions
On Tue, May 12, 2015 at 11:37 AM, Alvaro Herrera
alvhe...@2ndquadrant.com wrote:
Michael Paquier wrote:
On Tue, May 12, 2015 at 7:16 AM, Alvaro Herrera alvhe...@alvh.no-ip.org
wrote:
Allow on-the-fly capture of DDL event details
This feature lets user code inspect and take action on DDL
pg_upgrade: use single or double-quotes in command-line strings
This is platform-dependent.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/9d15292cfc581d2916778b79df0f0e86e032a677
Modified Files
--
src/bin/pg_upgrade/check.c | 12 +++-
Fix incorrect checking of deferred exclusion constraint after a HOT update.
If a row that potentially violates a deferred exclusion constraint is
HOT-updated later in the same transaction, the exclusion constraint would
be reported as violated when the check finally occurs, even if the row(s)
the
Fix incorrect checking of deferred exclusion constraint after a HOT update.
If a row that potentially violates a deferred exclusion constraint is
HOT-updated later in the same transaction, the exclusion constraint would
be reported as violated when the check finally occurs, even if the row(s)
the
Fix incorrect checking of deferred exclusion constraint after a HOT update.
If a row that potentially violates a deferred exclusion constraint is
HOT-updated later in the same transaction, the exclusion constraint would
be reported as violated when the check finally occurs, even if the row(s)
the
Fix incorrect checking of deferred exclusion constraint after a HOT update.
If a row that potentially violates a deferred exclusion constraint is
HOT-updated later in the same transaction, the exclusion constraint would
be reported as violated when the check finally occurs, even if the row(s)
the
Fix incorrect checking of deferred exclusion constraint after a HOT update.
If a row that potentially violates a deferred exclusion constraint is
HOT-updated later in the same transaction, the exclusion constraint would
be reported as violated when the check finally occurs, even if the row(s)
the
Increase threshold for multixact member emergency autovac to 50%.
Analysis by Noah Misch shows that the 25% threshold set by commit
53bb309d2d5a9432d2602c93ed18e58bd2924e15 is lower than any other,
similar autovac threshold. While we don't know exactly what value
will be optimal for all users,
Increase threshold for multixact member emergency autovac to 50%.
Analysis by Noah Misch shows that the 25% threshold set by commit
53bb309d2d5a9432d2602c93ed18e58bd2924e15 is lower than any other,
similar autovac threshold. While we don't know exactly what value
will be optimal for all users,
docs: add serialization anomaly to transaction isolation table
Also distinguish between SQL-standard and Postgres behavior.
Report by David G. Johnston
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/23c33198b961f27c80655a7cf439d49ef5a1833d
Modified Files
initdb: only recommend pg_ctl to start the server
Previously we mentioned the 'postgres' binary method as well.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/2200713aa8bb857ae2737f659073907628c9e2ca
Modified Files
--
src/bin/initdb/initdb.c |4
Increase threshold for multixact member emergency autovac to 50%.
Analysis by Noah Misch shows that the 25% threshold set by commit
53bb309d2d5a9432d2602c93ed18e58bd2924e15 is lower than any other,
similar autovac threshold. While we don't know exactly what value
will be optimal for all users,
Fix incorrect checking of deferred exclusion constraint after a HOT update.
If a row that potentially violates a deferred exclusion constraint is
HOT-updated later in the same transaction, the exclusion constraint would
be reported as violated when the check finally occurs, even if the row(s)
the
28 matches
Mail list logo
