1997-04-02 05:23:38 +02:00
|
|
|
/*-------------------------------------------------------------------------
|
|
|
|
*
|
1999-02-14 00:22:53 +01:00
|
|
|
* sequence.h
|
1997-09-07 07:04:48 +02:00
|
|
|
* prototypes for sequence.c.
|
1997-04-02 05:23:38 +02:00
|
|
|
*
|
2015-01-06 17:43:47 +01:00
|
|
|
* Portions Copyright (c) 1996-2015, PostgreSQL Global Development Group
|
2001-08-16 22:38:56 +02:00
|
|
|
* Portions Copyright (c) 1994, Regents of the University of California
|
|
|
|
*
|
2010-09-20 22:08:53 +02:00
|
|
|
* src/include/commands/sequence.h
|
1997-04-02 05:23:38 +02:00
|
|
|
*
|
|
|
|
*-------------------------------------------------------------------------
|
|
|
|
*/
|
|
|
|
#ifndef SEQUENCE_H
|
|
|
|
#define SEQUENCE_H
|
|
|
|
|
Revamp the WAL record format.
Each WAL record now carries information about the modified relation and
block(s) in a standardized format. That makes it easier to write tools that
need that information, like pg_rewind, prefetching the blocks to speed up
recovery, etc.
There's a whole new API for building WAL records, replacing the XLogRecData
chains used previously. The new API consists of XLogRegister* functions,
which are called for each buffer and chunk of data that is added to the
record. The new API also gives more control over when a full-page image is
written, by passing flags to the XLogRegisterBuffer function.
This also simplifies the XLogReadBufferForRedo() calls. The function can dig
the relation and block number from the WAL record, so they no longer need to
be passed as arguments.
For the convenience of redo routines, XLogReader now disects each WAL record
after reading it, copying the main data part and the per-block data into
MAXALIGNed buffers. The data chunks are not aligned within the WAL record,
but the redo routines can assume that the pointers returned by XLogRecGet*
functions are. Redo routines are now passed the XLogReaderState, which
contains the record in the already-disected format, instead of the plain
XLogRecord.
The new record format also makes the fixed size XLogRecord header smaller,
by removing the xl_len field. The length of the "main data" portion is now
stored at the end of the WAL record, and there's a separate header after
XLogRecord for it. The alignment padding at the end of XLogRecord is also
removed. This compansates for the fact that the new format would otherwise
be more bulky than the old format.
Reviewed by Andres Freund, Amit Kapila, Michael Paquier, Alvaro Herrera,
Fujii Masao.
2014-11-20 16:56:26 +01:00
|
|
|
#include "access/xlogreader.h"
|
Change many routines to return ObjectAddress rather than OID
The changed routines are mostly those that can be directly called by
ProcessUtilitySlow; the intention is to make the affected object
information more precise, in support for future event trigger changes.
Originally it was envisioned that the OID of the affected object would
be enough, and in most cases that is correct, but upon actually
implementing the event trigger changes it turned out that ObjectAddress
is more widely useful.
Additionally, some command execution routines grew an output argument
that's an object address which provides further info about the executed
command. To wit:
* for ALTER DOMAIN / ADD CONSTRAINT, it corresponds to the address of
the new constraint
* for ALTER OBJECT / SET SCHEMA, it corresponds to the address of the
schema that originally contained the object.
* for ALTER EXTENSION {ADD, DROP} OBJECT, it corresponds to the address
of the object added to or dropped from the extension.
There's no user-visible change in this commit, and no functional change
either.
Discussion: 20150218213255.GC6717@tamriel.snowman.net
Reviewed-By: Stephen Frost, Andres Freund
2015-03-03 18:10:50 +01:00
|
|
|
#include "catalog/objectaddress.h"
|
2011-09-09 19:23:41 +02:00
|
|
|
#include "fmgr.h"
|
2014-11-06 12:52:08 +01:00
|
|
|
#include "lib/stringinfo.h"
|
2011-09-04 07:13:16 +02:00
|
|
|
#include "nodes/parsenodes.h"
|
|
|
|
#include "storage/relfilenode.h"
|
2003-11-09 22:30:38 +01:00
|
|
|
|
2000-11-30 02:47:33 +01:00
|
|
|
|
|
|
|
typedef struct FormData_pg_sequence
|
|
|
|
{
|
|
|
|
NameData sequence_name;
|
2001-08-16 22:38:56 +02:00
|
|
|
int64 last_value;
|
2008-05-17 01:36:05 +02:00
|
|
|
int64 start_value;
|
2001-08-16 22:38:56 +02:00
|
|
|
int64 increment_by;
|
|
|
|
int64 max_value;
|
|
|
|
int64 min_value;
|
|
|
|
int64 cache_value;
|
|
|
|
int64 log_cnt;
|
|
|
|
bool is_cycled;
|
|
|
|
bool is_called;
|
2000-11-30 02:47:33 +01:00
|
|
|
} FormData_pg_sequence;
|
|
|
|
|
|
|
|
typedef FormData_pg_sequence *Form_pg_sequence;
|
1997-11-26 02:14:33 +01:00
|
|
|
|
1997-09-07 07:04:48 +02:00
|
|
|
/*
|
2000-06-11 22:08:01 +02:00
|
|
|
* Columns of a sequence relation
|
1997-04-02 05:23:38 +02:00
|
|
|
*/
|
|
|
|
|
1997-09-07 07:04:48 +02:00
|
|
|
#define SEQ_COL_NAME 1
|
|
|
|
#define SEQ_COL_LASTVAL 2
|
2008-05-17 01:36:05 +02:00
|
|
|
#define SEQ_COL_STARTVAL 3
|
|
|
|
#define SEQ_COL_INCBY 4
|
|
|
|
#define SEQ_COL_MAXVALUE 5
|
|
|
|
#define SEQ_COL_MINVALUE 6
|
|
|
|
#define SEQ_COL_CACHE 7
|
|
|
|
#define SEQ_COL_LOG 8
|
|
|
|
#define SEQ_COL_CYCLE 9
|
|
|
|
#define SEQ_COL_CALLED 10
|
1997-04-02 05:23:38 +02:00
|
|
|
|
1997-09-07 07:04:48 +02:00
|
|
|
#define SEQ_COL_FIRSTCOL SEQ_COL_NAME
|
|
|
|
#define SEQ_COL_LASTCOL SEQ_COL_CALLED
|
1997-04-02 05:23:38 +02:00
|
|
|
|
2000-11-30 02:47:33 +01:00
|
|
|
/* XLOG stuff */
|
2001-03-22 05:01:46 +01:00
|
|
|
#define XLOG_SEQ_LOG 0x00
|
2000-11-30 02:47:33 +01:00
|
|
|
|
|
|
|
typedef struct xl_seq_rec
|
|
|
|
{
|
2001-03-22 05:01:46 +01:00
|
|
|
RelFileNode node;
|
2000-12-28 14:00:29 +01:00
|
|
|
/* SEQUENCE TUPLE DATA FOLLOWS AT THE END */
|
2000-11-30 02:47:33 +01:00
|
|
|
} xl_seq_rec;
|
|
|
|
|
2000-06-11 22:08:01 +02:00
|
|
|
extern Datum nextval(PG_FUNCTION_ARGS);
|
2005-10-03 01:50:16 +02:00
|
|
|
extern Datum nextval_oid(PG_FUNCTION_ARGS);
|
|
|
|
extern Datum currval_oid(PG_FUNCTION_ARGS);
|
|
|
|
extern Datum setval_oid(PG_FUNCTION_ARGS);
|
|
|
|
extern Datum setval3_oid(PG_FUNCTION_ARGS);
|
2005-06-07 09:08:35 +02:00
|
|
|
extern Datum lastval(PG_FUNCTION_ARGS);
|
2000-06-11 22:08:01 +02:00
|
|
|
|
2011-01-02 14:08:08 +01:00
|
|
|
extern Datum pg_sequence_parameters(PG_FUNCTION_ARGS);
|
|
|
|
|
Change many routines to return ObjectAddress rather than OID
The changed routines are mostly those that can be directly called by
ProcessUtilitySlow; the intention is to make the affected object
information more precise, in support for future event trigger changes.
Originally it was envisioned that the OID of the affected object would
be enough, and in most cases that is correct, but upon actually
implementing the event trigger changes it turned out that ObjectAddress
is more widely useful.
Additionally, some command execution routines grew an output argument
that's an object address which provides further info about the executed
command. To wit:
* for ALTER DOMAIN / ADD CONSTRAINT, it corresponds to the address of
the new constraint
* for ALTER OBJECT / SET SCHEMA, it corresponds to the address of the
schema that originally contained the object.
* for ALTER EXTENSION {ADD, DROP} OBJECT, it corresponds to the address
of the object added to or dropped from the extension.
There's no user-visible change in this commit, and no functional change
either.
Discussion: 20150218213255.GC6717@tamriel.snowman.net
Reviewed-By: Stephen Frost, Andres Freund
2015-03-03 18:10:50 +01:00
|
|
|
extern ObjectAddress DefineSequence(CreateSeqStmt *stmt);
|
|
|
|
extern ObjectAddress AlterSequence(AlterSeqStmt *stmt);
|
Make TRUNCATE ... RESTART IDENTITY restart sequences transactionally.
In the previous coding, we simply issued ALTER SEQUENCE RESTART commands,
which do not roll back on error. This meant that an error between
truncating and committing left the sequences out of sync with the table
contents, with potentially bad consequences as were noted in a Warning on
the TRUNCATE man page.
To fix, create a new storage file (relfilenode) for a sequence that is to
be reset due to RESTART IDENTITY. If the transaction aborts, we'll
automatically revert to the old storage file. This acts just like a
rewriting ALTER TABLE operation. A penalty is that we have to take
exclusive lock on the sequence, but since we've already got exclusive lock
on its owning table, that seems unlikely to be much of a problem.
The interaction of this with usual nontransactional behaviors of sequence
operations is a bit weird, but it's hard to see what would be completely
consistent. Our choice is to discard cached-but-unissued sequence values
both when the RESTART is executed, and at rollback if any; but to not touch
the currval() state either time.
In passing, move the sequence reset operations to happen before not after
any AFTER TRUNCATE triggers are fired. The previous ordering was not
logically sensible, but was forced by the need to minimize inconsistency
if the triggers caused an error. Transactional rollback is a much better
solution to that.
Patch by Steve Singer, rather heavily adjusted by me.
2010-11-17 22:42:18 +01:00
|
|
|
extern void ResetSequence(Oid seq_relid);
|
2013-10-03 22:17:18 +02:00
|
|
|
extern void ResetSequenceCaches(void);
|
1997-09-07 07:04:48 +02:00
|
|
|
|
Revamp the WAL record format.
Each WAL record now carries information about the modified relation and
block(s) in a standardized format. That makes it easier to write tools that
need that information, like pg_rewind, prefetching the blocks to speed up
recovery, etc.
There's a whole new API for building WAL records, replacing the XLogRecData
chains used previously. The new API consists of XLogRegister* functions,
which are called for each buffer and chunk of data that is added to the
record. The new API also gives more control over when a full-page image is
written, by passing flags to the XLogRegisterBuffer function.
This also simplifies the XLogReadBufferForRedo() calls. The function can dig
the relation and block number from the WAL record, so they no longer need to
be passed as arguments.
For the convenience of redo routines, XLogReader now disects each WAL record
after reading it, copying the main data part and the per-block data into
MAXALIGNed buffers. The data chunks are not aligned within the WAL record,
but the redo routines can assume that the pointers returned by XLogRecGet*
functions are. Redo routines are now passed the XLogReaderState, which
contains the record in the already-disected format, instead of the plain
XLogRecord.
The new record format also makes the fixed size XLogRecord header smaller,
by removing the xl_len field. The length of the "main data" portion is now
stored at the end of the WAL record, and there's a separate header after
XLogRecord for it. The alignment padding at the end of XLogRecord is also
removed. This compansates for the fact that the new format would otherwise
be more bulky than the old format.
Reviewed by Andres Freund, Amit Kapila, Michael Paquier, Alvaro Herrera,
Fujii Masao.
2014-11-20 16:56:26 +01:00
|
|
|
extern void seq_redo(XLogReaderState *rptr);
|
|
|
|
extern void seq_desc(StringInfo buf, XLogReaderState *rptr);
|
2014-09-19 15:17:12 +02:00
|
|
|
extern const char *seq_identify(uint8 info);
|
2001-10-28 07:26:15 +01:00
|
|
|
|
2001-11-05 18:46:40 +01:00
|
|
|
#endif /* SEQUENCE_H */
|