|
|
|
|
/*-------------------------------------------------------------------------
|
|
|
|
|
*
|
|
|
|
|
* nodeModifyTable.h
|
|
|
|
|
*
|
|
|
|
|
*
|
|
|
|
|
* Portions Copyright (c) 1996-2018, PostgreSQL Global Development Group
|
|
|
|
|
* Portions Copyright (c) 1994, Regents of the University of California
|
|
|
|
|
*
|
|
|
|
|
* src/include/executor/nodeModifyTable.h
|
|
|
|
|
*
|
|
|
|
|
*-------------------------------------------------------------------------
|
|
|
|
|
*/
|
|
|
|
|
#ifndef NODEMODIFYTABLE_H
|
|
|
|
|
#define NODEMODIFYTABLE_H
|
|
|
|
|
|
|
|
|
|
#include "nodes/execnodes.h"
|
|
|
|
|
|
|
|
|
|
extern ModifyTableState *ExecInitModifyTable(ModifyTable *node, EState *estate, int eflags);
|
|
|
|
|
extern void ExecEndModifyTable(ModifyTableState *node);
|
|
|
|
|
extern void ExecReScanModifyTable(ModifyTableState *node);
|
MERGE SQL Command following SQL:2016
MERGE performs actions that modify rows in the target table
using a source table or query. MERGE provides a single SQL
statement that can conditionally INSERT/UPDATE/DELETE rows
a task that would other require multiple PL statements.
e.g.
MERGE INTO target AS t
USING source AS s
ON t.tid = s.sid
WHEN MATCHED AND t.balance > s.delta THEN
UPDATE SET balance = t.balance - s.delta
WHEN MATCHED THEN
DELETE
WHEN NOT MATCHED AND s.delta > 0 THEN
INSERT VALUES (s.sid, s.delta)
WHEN NOT MATCHED THEN
DO NOTHING;
MERGE works with regular and partitioned tables, including
column and row security enforcement, as well as support for
row, statement and transition triggers.
MERGE is optimized for OLTP and is parameterizable, though
also useful for large scale ETL/ELT. MERGE is not intended
to be used in preference to existing single SQL commands
for INSERT, UPDATE or DELETE since there is some overhead.
MERGE can be used statically from PL/pgSQL.
MERGE does not yet support inheritance, write rules,
RETURNING clauses, updatable views or foreign tables.
MERGE follows SQL Standard per the most recent SQL:2016.
Includes full tests and documentation, including full
isolation tests to demonstrate the concurrent behavior.
This version written from scratch in 2017 by Simon Riggs,
using docs and tests originally written in 2009. Later work
from Pavan Deolasee has been both complex and deep, leaving
the lead author credit now in his hands.
Extensive discussion of concurrency from Peter Geoghegan,
with thanks for the time and effort contributed.
Various issues reported via sqlsmith by Andreas Seltenreich
Authors: Pavan Deolasee, Simon Riggs
Reviewer: Peter Geoghegan, Amit Langote, Tomas Vondra, Simon Riggs
Discussion:
https://postgr.es/m/CANP8+jKitBSrB7oTgT9CY2i1ObfOt36z0XMraQc+Xrz8QB0nXA@mail.gmail.com
https://postgr.es/m/CAH2-WzkJdBuxj9PO=2QaO9-3h3xGbQPZ34kJH=HukRekwM-GZg@mail.gmail.com
8 years ago
|
|
|
extern TupleTableSlot *ExecPrepareTupleRouting(ModifyTableState *mtstate,
|
|
|
|
|
EState *estate,
|
|
|
|
|
struct PartitionTupleRouting *proute,
|
|
|
|
|
ResultRelInfo *targetRelInfo,
|
|
|
|
|
TupleTableSlot *slot);
|
|
|
|
|
extern TupleTableSlot *ExecDelete(ModifyTableState *mtstate,
|
|
|
|
|
ItemPointer tupleid, HeapTuple oldtuple, TupleTableSlot *planSlot,
|
|
|
|
|
EPQState *epqstate, EState *estate, bool *tupleDeleted,
|
|
|
|
|
bool processReturning, HeapUpdateFailureData *hufdp,
|
|
|
|
|
MergeActionState *actionState, bool canSetTag);
|
|
|
|
|
extern TupleTableSlot *ExecUpdate(ModifyTableState *mtstate,
|
|
|
|
|
ItemPointer tupleid, HeapTuple oldtuple, TupleTableSlot *slot,
|
|
|
|
|
TupleTableSlot *planSlot, EPQState *epqstate, EState *estate,
|
|
|
|
|
bool *tuple_updated, HeapUpdateFailureData *hufdp,
|
|
|
|
|
MergeActionState *actionState, bool canSetTag);
|
|
|
|
|
extern TupleTableSlot *ExecInsert(ModifyTableState *mtstate,
|
|
|
|
|
TupleTableSlot *slot,
|
|
|
|
|
TupleTableSlot *planSlot,
|
|
|
|
|
EState *estate,
|
|
|
|
|
MergeActionState *actionState,
|
|
|
|
|
bool canSetTag);
|
|
|
|
|
|
Phase 2 of pgindent updates.
Change pg_bsd_indent to follow upstream rules for placement of comments
to the right of code, and remove pgindent hack that caused comments
following #endif to not obey the general rule.
Commit e3860ffa4dd0dad0dd9eea4be9cc1412373a8c89 wasn't actually using
the published version of pg_bsd_indent, but a hacked-up version that
tried to minimize the amount of movement of comments to the right of
code. The situation of interest is where such a comment has to be
moved to the right of its default placement at column 33 because there's
code there. BSD indent has always moved right in units of tab stops
in such cases --- but in the previous incarnation, indent was working
in 8-space tab stops, while now it knows we use 4-space tabs. So the
net result is that in about half the cases, such comments are placed
one tab stop left of before. This is better all around: it leaves
more room on the line for comment text, and it means that in such
cases the comment uniformly starts at the next 4-space tab stop after
the code, rather than sometimes one and sometimes two tabs after.
Also, ensure that comments following #endif are indented the same
as comments following other preprocessor commands such as #else.
That inconsistency turns out to have been self-inflicted damage
from a poorly-thought-through post-indent "fixup" in pgindent.
This patch is much less interesting than the first round of indent
changes, but also bulkier, so I thought it best to separate the effects.
Discussion: https://postgr.es/m/E1dAmxK-0006EE-1r@gemulon.postgresql.org
Discussion: https://postgr.es/m/30527.1495162840@sss.pgh.pa.us
9 years ago
|
|
|
#endif /* NODEMODIFYTABLE_H */
|
