From: | hubert depesz lubaczewski <depesz(at)depesz(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Strange problem with create table as select * from table; |
Date: | 2011-11-04 22:43:48 |
Message-ID: | 20111104224348.GA3259@depesz.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
On Fri, Nov 04, 2011 at 05:49:44PM -0400, Tom Lane wrote:
> You said that pg_dump does not show the corruption. That could be
> because the data is coming out through the COPY code path instead of
> the SELECT code path. Could you try a pg_dump with --inserts (which
> will fetch the data with SELECTs) and see if it shows corrupt data?
i'm running the pg_dump (it will take some time, so don't hold your
breath), but at the same time - I can select these rows, correctly, with
normal SELECT from table (xobjects table). Doesn't it disprove this
theory?
Best regards,
depesz
--
The best thing about modern society is how easy it is to avoid contact with it.
http://depesz.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2011-11-04 23:04:34 | Re: Strange problem with create table as select * from table; |
Previous Message | Ivan Mincik | 2011-11-04 22:26:59 | PostgreSQL table history tracking |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2011-11-04 23:04:34 | Re: Strange problem with create table as select * from table; |
Previous Message | hubert depesz lubaczewski | 2011-11-04 22:25:49 | Re: Strange problem with create table as select * from table; |