Re: initdb failure (was Re: [GENERAL] sequence's plpgsql) - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: initdb failure (was Re: [GENERAL] sequence's plpgsql)
Date
Msg-id Pine.LNX.4.44.0309271129100.11938-100000@peter.localdomain
Whole thread Raw
In response to Re: initdb failure (was Re: [GENERAL] sequence's plpgsql)  (Jon Jensen <jon@endpoint.com>)
Responses Re: initdb failure (was Re: [GENERAL] sequence's plpgsql)
List pgsql-hackers
Jon Jensen writes:

> I hate to mention it, but would it be useful/non-overkill to make either
> of those things (context message maximum length and funny character
> escaping) configurable somehow?

I'm thinking the same.  We have conflicting needs of different groups:
Users on "real" Unix platforms converting old data need the checks, users
on Windows platforms with new data don't want them.  (I wonder what people
on Mac OS that mix Unix-style and native applications would want.)

-- 
Peter Eisentraut   peter_e@gmx.net



pgsql-hackers by date:

Previous
From: Stephan Szabo
Date:
Subject: Re: invalid tid errors in latest 7.3.4 stable.
Next
From: Richard Huxton
Date:
Subject: Re: 2-phase commit