I wrote:
> If it's just a quick kill, then there's a totally separate bug here for
> Windows. What is likely to happen with the current coding is that a
> failing child thread will queue its error message into the communication
> pipe, and then exit(1), thereby killing the whole pg_dump process be
Rather belatedly, I've started to look into a fix for pg_dump's
problem with error reporting in parallel mode:
http://www.postgresql.org/message-id/2458.1450894...@sss.pgh.pa.us
One of the issues here is that pg_dump uses threads not subprocesses
to do parallelism on Windows, which means that tota
On mån, 2011-12-05 at 15:04 -0300, Alvaro Herrera wrote:
> Having had to battle some exit() calls in the PHP interpreter back
> when
> I was working in PL/php, I agree that they shouldn't be there --
> abort()
> seems more appropriate if the system is truly busted. As for the
> fr-print.c code, I'
Excerpts from Peter Eisentraut's message of lun dic 05 14:27:41 -0300 2011:
> The cases in libpq are
>
> * various places in fe-print.c calling exit(1) when malloc fails,
> presumably having run out of memory, and
> * in libpq-int.h the macro PGTHREAD_ERROR, which is called i
Debian's package policy and quality check tool lintian reports the
following (among other things) on the postgresql-9.1 (and earlier)
packages:
X: libpq5: shlib-calls-exit usr/lib/libpq.so.5.4
X: libecpg6: shlib-calls-exit usr/lib/libecpg.so.6.3
which is explained as
I: shlib-calls-exit
N:
N:
Marcos Fabrício Corso wrote:
I would like to leave the list ...
Not really a question worth posting several lists. If you don't know how
to unsubscribe, try starting with the form linked from here.
http://www.postgresql.org/community/lists/
--
Richard Huxton
Archonet Ltd
--
I
would
like
to
leave
the
list
...
--
Acelerador POP
Acelere a sua conexão discada em até 19 x. Use o Acelerador POP. É grátis, pegue já o seu.
http://www.pop.com.br/acelerador
Peter Galantha <[EMAIL PROTECTED]> writes:
> Hi hackers,
> there was a hardware failure 'couse we had to turn off the computer manually.
> After the hardware change, the database reports exit status 512.
> Can anybody help me what 'Startup proc 850 exited with status 512' mean?
You're showing us
Hi hackers,
there was a hardware failure 'couse we had to turn off the computer manually.
After the hardware change, the database reports exit status 512.
Can anybody help me what 'Startup proc 850 exited with status 512' mean?
how can I solve this problem?
Peter Galantha
argosz at tensa.net
-
