William Garrison <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> What do you mean by "one batch" exactly? Both CREATE and DROP TABLESPACE
>> refuse to run in a transaction block, so I'm confused about this.
> Not a transaction block. A batch of commands submitted to the server in
> a single ca
Not a transaction block. A batch of commands submitted to the server in
a single call. In MSSQL land, I call that a batch. I don't know the
PostgreSql term. If you are using the pgadmin3 GUI, then I mean pressing
F5 once is a single batch. Pressing it twice is two batches.
The following wi
William Garrison <[EMAIL PROTECTED]> writes:
> -- Drop the tablespace and re-create in in an invalid location
> -- This only causes the bug if both these commands are run in one batch
What do you mean by "one batch" exactly? Both CREATE and DROP TABLESPACE
refuse to run in a transaction block, so
Postgres 8.2.3 on Windows Server 2003. I looked into this more, and I
narrowed the bug down. It only happens if you issue a DROP TABLESPACE
command and a CREATE TABLESPACE command in one batch, where the CREATE
TABLESPACE command points to an invalid location. I didn't realize how
obscure an
What version of PostgreSQL is this? Please provide the SQL commands
that cause this problem, with error output.
---
William Garrison wrote:
> On Windows Server 2003, if you create a tablespace to a location that
> doesn't
On Windows Server 2003, if you create a tablespace to a location that
doesn't exist, then try to remove that tablespace, you get an error that
pg_tblspc/# does not exist. It appears that postgres created the
tablespace internally, but not the folder. When you try to drop the
tablespace, t
