pg_proc without oid?
in [PgSql]
|
From: Peter Eisentraut on 19 Feb 2007 13:30 Tom Lane wrote: > SQL script maybe, much along the lines Greg was just mentioning. I would welcome that, although a similar suggestion was rejected a few years ago, which is why I didn't pursue it here. > you can't just decide to leave out a few OIDs on the > spur of the moment. I still don't understand why that would be a problem, aside from the fmgrtab problem that is specific to pg_proc. Other system catalogs also have mixed entries with and without explicit OIDs. -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---------------------------(end of broadcast)--------------------------- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
From: Magnus Hagander on 20 Feb 2007 03:24 On Mon, Feb 19, 2007 at 11:18:36AM -0500, Tom Lane wrote: > Peter Eisentraut <peter_e(a)gmx.net> writes: > > Am Montag, 19. Februar 2007 16:50 schrieb Tom Lane: > >> In the second place, if you don't want to predetermine OIDs for your > >> functions then they shouldn't be in hardwired pg_proc.h rows at all. > > > Where else would you put them? > > SQL script maybe, much along the lines Greg was just mentioning. > (I'd been thinking myself earlier that pg_amop/amproc/etc would be a > whole lot easier to maintain if we could feed CREATE OPERATOR CLASS > commands to the bootstrap process.) But getting there will take > nontrivial work; you can't just decide to leave out a few OIDs on the > spur of the moment. > > Magnus, I'd suggest reverting whatever you did to your MSVC script, > so we'll find out the next time someone makes this mistake... Ok. Will do once the entires in pg_proc are changed, so that I can still build. BTW, another problem with the stuff that's in there now - pg_proc.h contains description entries for the functions, but that never goes in to pg_description, since there is no oid to bind it to... //Magnus ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings
From: Peter Eisentraut on 20 Feb 2007 05:07 Am Dienstag, 20. Februar 2007 09:24 schrieb Magnus Hagander: > Ok. Will do once the entires in pg_proc are changed, so that I can still > build. It's done. -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings
From: Magnus Hagander on 21 Feb 2007 07:30 On Mon, Feb 19, 2007 at 11:18:36AM -0500, Tom Lane wrote: > > Magnus, I'd suggest reverting whatever you did to your MSVC script, > so we'll find out the next time someone makes this mistake... > Reverted. I left the part in genbki.pl in there, because that's a plain bug that was exposed by this, and could at least theoretically be exposed in other ways as well. //Magnus ---------------------------(end of broadcast)--------------------------- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to majordomo(a)postgresql.org so that your message can get through to the mailing list cleanly
First
|
Prev
|
Pages: 1 2 3 Prev: New feature request: FlashBack Query Next: Implicit casts with generic arrays |