Tatsuo Ishii wrote:
> Sent: Sunday, May 08, 2005 12:01 PM
> To: [EMAIL PROTECTED]
> Cc: pgsql-general@postgresql.org; pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] [GENERAL] Invalid unicode in COPY problem
>
> We have developed patches which relaxes the character
> validation so that Post
Madison Kelly wrote:
>Under most circumstances I would agree with you completely. In my
> case though I have to decide between risking a loss of a
> user's data or
> attempt to store the file name in some manner that would
> return the same
> name used by the file system.
>
>The user
Tatsuo Ishii wrote:
> Sent: Sunday, May 08, 2005 3:31 PM
> To: John Hansen
> Cc: [EMAIL PROTECTED]; pgsql-general@postgresql.org;
> pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] [GENERAL] Invalid unicode in COPY problem
>
> > Tatsuo Ishii wrote:
> > > Se
fixed
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Michael Fuhr
> Sent: Sunday, December 05, 2004 9:41 AM
> To: [EMAIL PROTECTED]
> Subject: [GENERAL] List archives search function broken
>
> Using the list archive search function currently fai
> > Using the list archive search function currently fails with
> > 503 Service Unavailable.
> >
> > Should messages about list archive problems go to pgsql-general, or
> > would it be better to use one of the other lists like bugs, hackers,
> > or www?
>
> I think complaints should go to -www l
> John,
>
> you could always rely on your script where you check if db
> handler is alive and if not then show gentle error message
> with link to www.pgsql.ru
I never check if dbhandler is alive in the frontend
This was the backend OS that shut down, which also hosts the filesystems
for th
