Cyril VELTER wrote:
De : mailto:[EMAIL PROTECTED]
Cyril VELTER wrote:
Is length() supposed to return the very high length in case of corruption
?
You'd have thought it would. The odd thing (if it is data corruption) is
that you would expect to see something in the server logs about a
failur
De : mailto:[EMAIL PROTECTED]
> Cyril VELTER wrote:
> >
> > Is length() supposed to return the very high length in case of
> > corruption
?
>
> You'd have thought it would. The odd thing (if it is data corruption) is
> that you would expect to see something in the server logs about a
> fa
Cyril VELTER wrote:
I have run the following query to get all record with one field over
10MB :
select
p2,length(p18155),length(p18154),length(p4065),length(p4083),length(p4020),lengt
h(p4074),length(p3857),length(p32402),length(p5512),length(p18175) from c2674
where length(p18155)>1
De : mailto:[EMAIL PROTECTED]
> "Cyril VELTER" <[EMAIL PROTECTED]> writes:
> > The server have 4G of ram. But doing a search in the source code it
> > does
not
> > seem that these values are used during a copy operation.
>
> They aren't. The "out of memory" complaint sounds more like it m
"Cyril VELTER" <[EMAIL PROTECTED]> writes:
> The server have 4G of ram. But doing a search in the source code it
> does not
> seem that these values are used during a copy operation.
They aren't. The "out of memory" complaint sounds more like it might be
due to corrupt data, ie the olde s
Cyril VELTER wrote:
It's just that 8.2.4 has a fix that says:
Allow pg_dump to do binary backups larger than two gigabytes on Windows
(Magnus)
Now, whether that will affect you I'm not sure, since you said you were
dumping from Linux, with the server on Windows.
I don't think so. The dump
De : mailto:[EMAIL PROTECTED]
> Cyril VELTER wrote:
> >
> > maintenance_work_mem and work_mem are set to their default value (16M /
1M).
> > Does Copy use any of these values ? The doc only state sort operations for
> > work_mem and vacuum / create index / alter table add foreing key for
Cyril VELTER wrote:
I recently upgraded a 8.0 database to 8.2 (server is running windows 2003
server) and now I cannot dump the database any more.
At some point in the dump, pg_dump (run on a centos 3 linux) return :
pg_dump: Dumping the contents of table "c2674" failed: PQgetCopyData()
