From: | "Donald Fraser" <postgres(at)kiwi-fraser(dot)net> |
---|---|
To: | "[JDBC]" <pgsql-jdbc(at)postgresql(dot)org>, "[ADMIN]" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Missing documentation for error code: 80S01 |
Date: | 2011-04-12 16:04:31 |
Message-ID: | 3670D8885C9549A393E47A0C1582B07A@DEVELOP1 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-bugs pgsql-jdbc |
----- Original Message -----
From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
> "Donald Fraser" <postgres(at)kiwi-fraser(dot)net> wrote:
>
>> I was expecting the code to be something like: crash_shutdown,
>> however that appears to be under a completely different error
>> class: 57P02.
>
> If a JDBC client detects that the connection is broken, how would it
> know that it is because the server crashed?
>
You are correct how could it. However the JDBC driver does know
that the server has terminated the connection and not an
IO error (via end of stream or EOF).
Is the error class "57" a better prefix for this type of error?
Knowing that the the only options for server shut down are:
Admin shut-down or Crash shut-down ?
Regards
Donald
From | Date | Subject | |
---|---|---|---|
Next Message | Gabriele Bartolini | 2011-04-12 16:04:40 | Re: what is a serial_fkey data type? |
Previous Message | Kevin Grittner | 2011-04-12 15:36:50 | Re: Missing documentation for error code: 80S01 |
From | Date | Subject | |
---|---|---|---|
Next Message | Shianmiin | 2011-04-12 17:48:54 | Re: PostgreSQL backend process high memory usage issue |
Previous Message | Kevin Grittner | 2011-04-12 15:36:50 | Re: Missing documentation for error code: 80S01 |
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2011-04-12 19:16:02 | Re: Missing documentation for error code: 80S01 |
Previous Message | Kevin Grittner | 2011-04-12 15:36:50 | Re: Missing documentation for error code: 80S01 |