Added to TODO:
o Prevent concurrent CREATE TABLE table1 from sometimes returning
a cryptic error message
http://archives.postgresql.org/pgsql-bugs/2007-10/msg00169.php
---
Bill Moran wrote:
>
In response to Alvaro Herrera <[EMAIL PROTECTED]>:
> Bill Moran wrote:
> > In response to Tom Lane <[EMAIL PROTECTED]>:
> >
> > > "Bill Moran" <[EMAIL PROTECTED]> writes:
> > > > Issuing a statement like:
> > > > CREATE TABLE table2 AS SELECT * FROM table1;
> > > > simultaneously in two separate
Bill Moran wrote:
> In response to Tom Lane <[EMAIL PROTECTED]>:
>
> > "Bill Moran" <[EMAIL PROTECTED]> writes:
> > > Issuing a statement like:
> > > CREATE TABLE table2 AS SELECT * FROM table1;
> > > simultaneously in two separate sessions should result in an error like
> > > "ERROR: relation "t
In response to Tom Lane <[EMAIL PROTECTED]>:
> "Bill Moran" <[EMAIL PROTECTED]> writes:
> > Issuing a statement like:
> > CREATE TABLE table2 AS SELECT * FROM table1;
> > simultaneously in two separate sessions should result in an error like
> > "ERROR: relation "table2" already exists" (in one o
"Bill Moran" <[EMAIL PROTECTED]> writes:
> Issuing a statement like:
> CREATE TABLE table2 AS SELECT * FROM table1;
> simultaneously in two separate sessions should result in an error like
> "ERROR: relation "table2" already exists" (in one or the other of the
> sessions, depending on the exact ti
