pgsql: Implement remaining fields of information_schema.sequences view
Implement remaining fields of information_schema.sequences view
Add new function pg_sequence_parameters that returns a sequence's start,
minimum, maximum, increment, and cycle values, and use that in the view.
(bug #5662; design suggestion by Tom Lane)
Also slightly adjust the view's column order and permissions after review of
SQL standard.
Branch
------
master
Details
-------
http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=39b88432968a2f4c01c20948f12bf9c8e388474d
Modified Files
--------------
doc/src/sgml/information_schema.sgml | 27 ++++++++++----
src/backend/catalog/information_schema.sql | 12 ++++---
src/backend/commands/sequence.c | 51 ++++++++++++++++++++++++++++
src/include/catalog/catversion.h | 2 +-
src/include/catalog/pg_proc.h | 2 +
src/include/commands/sequence.h | 2 +
src/test/regress/expected/sequence.out | 7 ++++
src/test/regress/sql/sequence.sql | 3 ++
8 files changed, 92 insertions(+), 14 deletions(-)
peter_e@gmx.net (Peter Eisentraut) writes:
Implement remaining fields of information_schema.sequences view
Add new function pg_sequence_parameters that returns a sequence's start,
minimum, maximum, increment, and cycle values, and use that in the view.
(bug #5662; design suggestion by Tom Lane)Also slightly adjust the view's column order and permissions after review of
SQL standard.
Is there a particular reason that the start/min/max/inc values are now
being cast to character_data, rather than integer, as they have been? I
have some views I'm using that just broke because of this.
I'd rather not work around this if it's not necessary, and it doesn't
seem to make sense for these values to be of other than a numeric type
(and likely BIGINT, as that's what pg_sequence_parameters() returns).
--
(reverse (concatenate 'string "ofni.secnanifxunil" "@" "enworbbc"))
http://www3.sympatico.ca/cbbrowne/slony.html
E.V.A., pod 5, launching...