Re: Accessing schema data in information schema
Jim C. Nasby <jnasby@pervasive.com>
From: "Jim C. Nasby" <jnasby@pervasive.com>
To: Hannu Krosing <hannu@skype.net>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Peter Eisentraut <peter_e@gmx.net>, pgsql-hackers@postgresql.org
Date: 2006-03-23T16:31:57Z
Lists: pgsql-hackers
On Thu, Mar 23, 2006 at 12:10:54AM +0200, Hannu Krosing wrote: > ??hel kenal p??eval, K, 2006-03-22 kell 16:11, kirjutas Tom Lane: > > Peter Eisentraut <peter_e@gmx.net> writes: > > > How does one get at the missing fields. The only way I know is > > > selecting from the sequence, but how does one work this into this > > > query? Somehow it seems that these things should be stored in a real > > > system catalog. > > > > Yeah. I've occasionally toyed with the idea that sequences should be > > rows in a single catalog instead of independent tables as they are now. > > This would make for a much smaller disk footprint (with consequent I/O > > savings) and would solve problems like the one you have. > > Would it not make page locking problems much worse with all get_next()'s > competeing to update the same page? What about bumping up the default cache setting a bit? Even going to a fairly conservative value, like 10 or 25 would probably make a huge difference. -- Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com Pervasive Software http://pervasive.com work: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461