Thanx for tip, Tom. I'll definitely give that a try in my spare time.
Cheers,
Kevin
Tom Lane wrote:
Kevin Neufeld <[EMAIL PROTECTED]> writes:
Tom Lane wrote:
A superuser can create whatever he wants in pg_catalog. Whether this
is a good idea or will behave smoothly is a topic that has not be
Kevin Neufeld <[EMAIL PROTECTED]> writes:
>> Tom Lane wrote:
>>> A superuser can create whatever he wants in pg_catalog. Whether this
>>> is a good idea or will behave smoothly is a topic that has not been
>>> thought about, to my knowledge.
> Sorry, Tom. I think you are mistaken. In my 8.3 inst
Tom Lane wrote:
A superuser can create whatever he wants in pg_catalog. Whether this
is a good idea or will behave smoothly is a topic that has not been
thought about, to my knowledge.
regards, tom lane
Sorry, Tom. I think you are mistaken. In my 8.3 instance, system
catalo
Really? I didn't know that ... guess I never tried. I'll have to do
some experimenting! Thanx Tom.
-- Kevin
Tom Lane wrote:
Kevin Neufeld <[EMAIL PROTECTED]> writes:
This might seem like a silly question, but what are the implications of
PostgreSQL allowing developers to create custom catal
Kevin Neufeld <[EMAIL PROTECTED]> writes:
> This might seem like a silly question, but what are the implications of
> PostgreSQL allowing developers to create custom catalogs?
> For example, PostgreSQL currently uses the pg_catalog schema to store
> system catalogs / relations / functions / etc.
This might seem like a silly question, but what are the implications of
PostgreSQL allowing developers to create custom catalogs?
For example, PostgreSQL currently uses the pg_catalog schema to store
system catalogs / relations / functions / etc. Has thought gone into
extending the scope to a
