peter_e(at)gmx(dot)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"))
E.V.A., pod 5, launching...
In response to
pgsql-hackers by date
|Next:||From: Joel Jacobson||Date: 2011-01-07 18:10:34|
|Previous:||From: Jeff Davis||Date: 2011-01-07 17:33:29|
|Subject: Re: WIP: Range Types|
pgsql-committers by date
|Next:||From: Tom Lane||Date: 2011-01-08 00:17:34|
|Subject: pgsql: Fix GIN to support null keys, empty and null items,and full ind|
|Previous:||From: Robert Haas||Date: 2011-01-07 16:09:03|
|Subject: Re: Re: [COMMITTERS] pgsql: New system view
pg_stat_replication displays activity of wal sen|