Hi,
I forgot to mention that we are using plphp version 1.1 but I guess that
in the process of making a pg_restore this issue does not really matter.
Thanks Mario.
Mario Lopez escribió:
Hi,
The platform as you have seen is Debian testing branch. I have
activated log_statement but again not
Mario Lopez <[EMAIL PROTECTED]> writes:
> PID:8069 CMD_TAG:idle XID:274157581 LOG: 0: sentencia: INSERT INTO
> scannmap4 VALUES (1719914, 2, 117, 28, 1155, 17073, 1, 1, '', '', '',
> '', NULL);
> PID:8069 CMD_TAG:idle XID:274157581 UBICACIÓN: log_after_parse,
> postgres.c:605
> PID:8025 CM
Hi,
The platform as you have seen is Debian testing branch. I have activated
log_statement but again nothing clear, the query that makes the system
fail has nothing strange on it here is a dump.
I do not know how toget a stack trace and the "crash" does not provide a
core dump :(. Could you
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> Maybe someone else has an idea? The previous-to-last message below is
> "server process exited with exit code 255".
That's very strange if the platform is Linux --- I was guessing it was
Windows.
Please try to get a core dump from the crash and provid
Hi again..
There are no kernel messages and I do not seem to find anything related
to this error code. The version installed is the last version available
in Debian testing branch:
postgresql-8.18.1.4-6
I have searched and there are not any known bugs about XID or pro
Hola,
Mario Lopez wrote:
> Hola Alvaro,
>
> The process that are being reaped are postgresql child processes, more
> precisely the process that is attending my queryes...
>
> Here I have another log that has the %p %i and %x in that order but I
> see no clear difference.
I see the same as you
Hola Alvaro,
The process that are being reaped are postgresql child processes, more
precisely the process that is attending my queryes...
Here I have another log that has the %p %i and %x in that order but I
see no clear difference.
Thanks.
Alvaro Herrera escribió:
Mario Lopez wrote:
Mario Lopez wrote:
> Hi Alvaro,
>
> Ok, maybe is not a crash but this issue makes postgresql reap all of
> it's child processes and restart operations, after this error I get in
> pg_restore this message:
>
> pg_restore: [archivador (bd)] Error durante PROCESAMIENTO DE TABLA DE
> CONTENIDOS:
Hi Alvaro,
Ok, maybe is not a crash but this issue makes postgresql reap all of
it's child processes and restart operations, after this error I get in
pg_restore this message:
pg_restore: [archivador (bd)] Error durante PROCESAMIENTO DE TABLA DE
CONTENIDOS:
pg_restore: [archivador (bd)] Err
Mario Lopez wrote:
> Hi!,
>
> I am having an XID issue with PostgreSQL, while doing a pg_restore from
> a 200MB saved database I get a server crash, searching through the debug
> messages I have found that PostgreSQL crashes due to a exausted XID
> resource with a message that looks this way (s
Hi!,
I am having an XID issue with PostgreSQL, while doing a pg_restore from
a 200MB saved database I get a server crash, searching through the debug
messages I have found that PostgreSQL crashes due to a exausted XID
resource with a message that looks this way (sorry for the Spanish log)
UB
11 matches
Mail list logo
