| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Zeugswetter Andreas DCP SD <ZeugswetterA(at)spardat(dot)at>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Accessing schema data in information schema |
| Date: | 2006-03-23 18:03:06 |
| Message-ID: | 4422E2DA.6020908@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
>Given the thought that we need both
>transactional and nontransactional state for a sequence, I'm kind of
>inclined to leave the transactional data in pg_class. We could still
>imagine putting the nontransactional state into a new pg_sequence
>catalog indexed by, say, the pg_class OID of the sequences. OTOH I'm
>not sure how much that buys for Peter's problem --- it might be better
>for him just to invent some functions that can grab the required data
>given the sequence OID.
>
>
>
Yes, this seems a lot of lifting for a fairly small need. If there
aren't other advantages, a simple function or two seems a better way to
go, and then there are no legacy problems.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2006-03-23 18:29:27 | Re: Where does the time go? |
| Previous Message | Tom Lane | 2006-03-23 17:47:35 | Re: Accessing schema data in information schema |