Search Postgresql Archives

Re: Fixing invalid owners on pg_toast tables in 8.3.5

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Cott Lang <cott@xxxxxxxxxxxxxxxxx> writes:
> I fiddled around a while, found the problem, and I can repeat it at
> will. It's actually related to type changes we've made over the months
> since the restore.

[ scratches head... ]  That example fails to misbehave for me in 8.3.6,
and I'm pretty certain there have been no relevant bugfixes since 8.3.5.
Can anyone else duplicate a change of toast table owner?

Are you by any chance using a nondefault block_size?  It strikes me that
at block_size 32K, the example would involve enlarging the varchar's
width across the boundary where a toast table would be created.  However
that still doesn't explain the results, since in that case the first
"select typowner" shouldn't have found any row.

Are both instances of the select finding the same pg_type row?  You've
phrased the select to hide all the evidence, but what we'd need to
figure out is whether reltoastrelid changed or the pg_type row itself
got updated.

			regards, tom lane

-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux