| 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 21:57:21 |
| Message-ID: | 20111104215721.GA1415@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?
Sure. Testing.
> Another thing we probably should ask at this point is whether you have
> any nonstandard software loaded into your server, like auto_explain
> or pg_stat_statements or some such.
No. Nothing like this. Just base Pg.
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 | mark | 2011-11-04 22:18:09 | inconsistent interval normalization |
| Previous Message | Tom Lane | 2011-11-04 21:49:44 | Re: Strange problem with create table as select * from table; |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-11-04 22:18:55 | Re: Strange problem with create table as select * from table; |
| Previous Message | Tom Lane | 2011-11-04 21:49:44 | Re: Strange problem with create table as select * from table; |