Dear Tom,
So my question still is: Given the fact that I have some use for these
oids, would it make sense to submit a patch to add them?
It will be rejected.
That's a simple a direct answer as I like them.
So I won't bother to submit a patch;-)
BTW, maybe you could reject some of the
Fabien COELHO wrote:
Dear Tom,
So my question still is: Given the fact that I have some use for these
oids, would it make sense to submit a patch to add them?
It will be rejected.
That's a simple a direct answer as I like them.
So I won't bother to submit a patch;-)
BTW,
Dear Bruce,
BTW, maybe you could reject some of the patches I submitted earlier,
rather than to simply ignore them?
The only outstanding patch I see from you is:
[PATCHES] [NOT] (LIKE|ILIKE) (ANY|SOME|ALL) (subquery...)
from March 29. I will put it in the queue now. Are there
Fabien COELHO [EMAIL PROTECTED] writes:
Sure:-)
Subject: [PATCHES] hint infrastructure setup (v3)
Oh, I was intending to review that but got caught up in functions-
returning-rowtypes hacking. I'll take a look as soon as I'm done
with the rowtypes project (should be in a day or two).
Fabien COELHO [EMAIL PROTECTED] writes:
I wish I had some way of referencing objects that I need to designate
(say, an attribute, an index, a table, a constraint, and so on).
AFAIK, all objects that you might need to designate can be identified
using the scheme employed in pg_depend and
Dear hackers,
I'm still trying to play with pg_catalog relations.
I notice that some tables in pg_catalog have oids, and some do not have
them (e.g. pg_attribute, pg_group, pg_shadow...). Also convenient
user-oriented views could reproduce the oid of their parent table
(e.g. pg_user if
Fabien COELHO [EMAIL PROTECTED] writes:
I notice that some tables in pg_catalog have oids, and some do not have
them (e.g. pg_attribute, pg_group, pg_shadow...).
That's not a bug, it's a feature. We don't use up OIDs on tables that
don't need them.
regards, tom lane
Dear Tom,
I notice that some tables in pg_catalog have oids, and some do not have
them (e.g. pg_attribute, pg_group, pg_shadow...).
That's not a bug, it's a feature. We don't use up OIDs on tables that
don't need them.
Sure. I did not suggest that this is a bug! I'm sorry if it sounded
