Re: CREATE/DROP SCHEMA considered harmful

From: Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: CREATE/DROP SCHEMA considered harmful
Date: 2000-08-20 18:16:01
Message-ID: 39A02061.9A1B129E@alumni.caltech.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> I think the create and drop schema commands should throw a "not
> implemented" error, rather than fiddle around with databases. Consider
> users that try these commands just on luck.
> Btw., the grammar for these commands isn't implemented correctly either.

Sure. I'm not too worried about them, since what you suggest can be done
at any time before release.

At the moment, I'm having trouble just getting a database installed. Did
something change recently? I *thought* I was tracking down a problem
where updated system catalogs did not get propagated into the
share/*.bki files. I did an update from cvsup a few minutes ago, and now
that seems to be fixed, but psql cannot create a database :(

The message when running createdb is:

psql: ConnectDBStart() -- connect() failed: Invalid argument
Is the postmaster running...

Ah, a "make distclean" seems to have fixed it for me. Not sure why it
would need to be that drastic; are we missing a dependency somewhere?

- Tom

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2000-08-20 18:18:39 Re: Optimisation deficiency: currval('seq')-->seq scan, constant-->index scan
Previous Message Tom Lane 2000-08-20 18:03:15 Re: Optimisation deficiency: currval('seq')-->seq scan, constant-->index scan