Re: Strange problem with create table as select * from table;

From: Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: depesz(at)depesz(dot)com, pgsql-general(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Strange problem with create table as select * from table;
Date: 2011-11-05 02:25:06
Message-ID: 201111041925.07038.adrian.klaver@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

On Friday, November 04, 2011 6:04:02 pm Tom Lane wrote:
> I wrote:
> > A different line of thought is that there's something about these
> > specific source rows, and only these rows, that makes them vulnerable to
> > corruption during INSERT/SELECT. Do they by any chance contain any
> > values that are unusual elsewhere in your table? One thing I'm
> > wondering about right now is the nulls bitmap --- so do these rows have
> > nulls (or not-nulls) in any place that's unusual elsewhere?
>
> Hah ... I have a theory.
>

>
> This is trivial to fix, now that we know there's a problem --- the
> function is only using that assumption to save itself a couple lines
> of code. Penny wise, pound foolish :-(

I killed a few brain cells just reading the explanation:)

>
> regards, tom lane
>
>

--
Adrian Klaver
adrian(dot)klaver(at)gmail(dot)com

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Stuart Bishop 2011-11-05 02:49:26 Re: Excessive planner time for some queries with high statistics
Previous Message Tom Lane 2011-11-05 01:04:02 Re: Strange problem with create table as select * from table;

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Smith 2011-11-05 02:29:58 Re: IDLE in transaction introspection
Previous Message Tom Lane 2011-11-05 01:04:02 Re: Strange problem with create table as select * from table;