Alvaro Herrera writes:
> Nagy Daniel wrote:
>> More info: we disabled autovacuum (we do vacuuming via cron)
>> and the segfaults seem to be gone.
> That's pretty weird if it means that autovacuum was crashing and your
> cron-based vacuums are not.
We've seen crashes in the autovac control logic
Nagy Daniel wrote:
> More info: we disabled autovacuum (we do vacuuming via cron)
> and the segfaults seem to be gone.
That's pretty weird if it means that autovacuum was crashing and your
cron-based vacuums are not.
--
Alvaro Herrerahttp://www.CommandPrompt.com/
On tor, 2009-12-03 at 19:02 -0500, Tom Lane wrote:
> Peter Eisentraut writes:
> > ... So you should not try to assign to
> > the parameters of a function.
>
> If it's allowed in normal Python functions, that definitely needs to be
> documented. Better would be to fix it or at least throw a more
More info: we disabled autovacuum (we do vacuuming via cron)
and the segfaults seem to be gone.
Daniel
Tom Lane wrote:
> Nagy Daniel writes:
>> I have pg segfaults on two boxes, a DL160G6 and a DL380g5.
>> I've just checked their memory with memtest86+ v2.11
>> No errors were detected.
>> We al
Yes, the file is there as of now and its contents are:
localhost:5432:*:postgres:bar
I am not sure if the file was there when it actually happened. But the repro
steps are complete in themselves and can be reproed on any fresh install of
ver 8.4.1.
Thanks,
Ashish.
On Sat, Dec 19, 2009 at 5:57 A
