On Jul 11, 2011, at 8:55 PM, Bruce Momjian wrote:
> Does this affect tables created during 9.1 beta? I assume a server
> restart fixes all this, but I am just checking.
Yes, I think a server restart will fix it, though there might be corner cases
I'm not thinking of.
...Robert
--
Sent via pgs
Robert Haas wrote:
> On Fri, Jul 1, 2011 at 10:32 AM, Robert Haas wrote:
> > On Fri, Jul 1, 2011 at 8:06 AM, Amit Khandekar
> > wrote:
> >> In 9.1, if a table is created using an explicit pg_temp qualification,
> >> the pg_class.relpersistence is marked 'p', not 't'.
> >
> > That's a bug. ?Thanks
On Fri, Jul 1, 2011 at 1:59 PM, Robert Haas wrote:
> On Fri, Jul 1, 2011 at 10:32 AM, Robert Haas wrote:
>> On Fri, Jul 1, 2011 at 8:06 AM, Amit Khandekar
>> wrote:
>>> In 9.1, if a table is created using an explicit pg_temp qualification,
>>> the pg_class.relpersistence is marked 'p', not 't'.
On Fri, Jul 1, 2011 at 10:32 AM, Robert Haas wrote:
> On Fri, Jul 1, 2011 at 8:06 AM, Amit Khandekar
> wrote:
>> In 9.1, if a table is created using an explicit pg_temp qualification,
>> the pg_class.relpersistence is marked 'p', not 't'.
>
> That's a bug. Thanks for the report.
OK, so I think
On Fri, Jul 1, 2011 at 8:06 AM, Amit Khandekar
wrote:
> In 9.1, if a table is created using an explicit pg_temp qualification,
> the pg_class.relpersistence is marked 'p', not 't'.
>
> postgres=# CREATE TABLE pg_temp.temptable (i int4);
> CREATE TABLE
>
> postgres=# select relpersistence from pg_c
In 9.1, if a table is created using an explicit pg_temp qualification,
the pg_class.relpersistence is marked 'p', not 't'.
postgres=# CREATE TABLE pg_temp.temptable (i int4);
CREATE TABLE
postgres=# select relpersistence from pg_class where relname = 'temptable';
relpersistence
