On tis, 2010-07-20 at 13:31 +0300, Marko Kreen wrote:
> > http://wiki.postgresql.org/wiki/Standard_conforming_strings
>
> There is two sorts of support:
>
> 1. Detect stdstr on startup and use that setting.
>
> 2. Detect online changes to stdstr and follow them.
>
> AFAICS psycopg does not sup
On 7/20/10, Peter Eisentraut wrote:
> On sön, 2010-07-18 at 09:42 -0700, David E. Wheeler wrote:
> > On Jul 18, 2010, at 1:35 AM, Peter Eisentraut wrote:
> >
> > > I think there are two ways we can do this, seeing that most appear to be
> > > in favor of doing it in the first place: Either we
On Mon, Jul 19, 2010 at 8:32 PM, Robert Haas wrote:
> On Mon, Jul 19, 2010 at 5:04 PM, Peter Eisentraut wrote:
>> On sön, 2010-07-18 at 09:42 -0700, David E. Wheeler wrote:
>>> On Jul 18, 2010, at 1:35 AM, Peter Eisentraut wrote:
>>>
>>> > I think there are two ways we can do this, seeing that mo
On Mon, Jul 19, 2010 at 5:04 PM, Peter Eisentraut wrote:
> On sön, 2010-07-18 at 09:42 -0700, David E. Wheeler wrote:
>> On Jul 18, 2010, at 1:35 AM, Peter Eisentraut wrote:
>>
>> > I think there are two ways we can do this, seeing that most appear to be
>> > in favor of doing it in the first plac
On sön, 2010-07-18 at 09:42 -0700, David E. Wheeler wrote:
> On Jul 18, 2010, at 1:35 AM, Peter Eisentraut wrote:
>
> > I think there are two ways we can do this, seeing that most appear to be
> > in favor of doing it in the first place: Either we just flip the
> > default, make a note in the rel
"David E. Wheeler" writes:
> On Jul 18, 2010, at 1:35 AM, Peter Eisentraut wrote:
>> I think there are two ways we can do this, seeing that most appear to be
>> in favor of doing it in the first place: Either we just flip the
>> default, make a note in the release notes, and see what happens. Or
On Jul 18, 2010, at 1:35 AM, Peter Eisentraut wrote:
> I think there are two ways we can do this, seeing that most appear to be
> in favor of doing it in the first place: Either we just flip the
> default, make a note in the release notes, and see what happens. Or we
> spend some time now and ma
On ons, 2010-07-14 at 10:48 -0400, Robert Haas wrote:
> On Fri, Jan 29, 2010 at 10:02 PM, Josh Berkus wrote:
> >> An actual plan here might look like "let's flip it before 9.1alpha1
> >> so we can get some alpha testing cycles on it" ...
> >
> > "Hey, let's flip it in 9.1 CF 1, so that we can have
Robert Haas writes:
> On Jul 15, 2010, at 12:30 AM, Richard Huxton wrote:
>> Any reason not to add a line to the 9.0 docs/release notes saying "WARNING:
>> The PGDG currently plan to change this setting's default in 9.1"?
> Well, mostly that we could change our mind if it makes too big a boom.
On Jul 15, 2010, at 12:30 AM, Richard Huxton wrote:
> On 14/07/10 15:48, Robert Haas wrote:
>> On Fri, Jan 29, 2010 at 10:02 PM, Josh Berkus wrote:
An actual plan here might look like "let's flip it before 9.1alpha1
so we can get some alpha testing cycles on it" ...
>>>
>>> "Hey, let's
On 14/07/10 15:48, Robert Haas wrote:
On Fri, Jan 29, 2010 at 10:02 PM, Josh Berkus wrote:
An actual plan here might look like "let's flip it before 9.1alpha1
so we can get some alpha testing cycles on it" ...
"Hey, let's flip it in 9.1 CF 1, so that we can have some alpha testing
cycles on i
Robert Haas writes:
> On Fri, Jan 29, 2010 at 10:02 PM, Josh Berkus wrote:
> An actual plan here might look like "let's flip it before 9.1alpha1
> so we can get some alpha testing cycles on it" ...
>>
>> "Hey, let's flip it in 9.1 CF 1, so that we can have some alpha testing
>> cycles on it."
>
Robert Haas wrote:
> On Fri, Jan 29, 2010 at 10:02 PM, Josh Berkus wrote:
> >> An actual plan here might look like "let's flip it before 9.1alpha1
> >> so we can get some alpha testing cycles on it" ...
> >
> > "Hey, let's flip it in 9.1 CF 1, so that we can have some alpha testing
> > cycles on i
On Fri, Jan 29, 2010 at 10:02 PM, Josh Berkus wrote:
>> An actual plan here might look like "let's flip it before 9.1alpha1
>> so we can get some alpha testing cycles on it" ...
>
> "Hey, let's flip it in 9.1 CF 1, so that we can have some alpha testing
> cycles on it."
Should we do this? Patch
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Are we going to turn on standard_conforming_strings for 8.3?
>
> I'd be inclined to wait a bit longer, i.e., 8.4, seeing that this is
> intended to be a short release cycle. 8.2 has not been out long enough
> to draw any meaningful c
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Are we going to turn on standard_conforming_strings for 8.3?
I'd be inclined to wait a bit longer, i.e., 8.4, seeing that this is
intended to be a short release cycle. 8.2 has not been out long enough
to draw any meaningful conclusions about whether we
Are we going to turn on standard_conforming_strings for 8.3? We
discussed the idea when we added it in 8.1, and enabled the backslash
warning in 8.2. We have gotten almost no pushback on the warning, so it
seems enabling it might be good. Right now, for default
postgresql.conf, users are getting
I see that in CVS head, if you turn on standard_conforming_strings,
it still whines about backslashes:
regression=# set standard_conforming_strings to 1;
SET
regression=# select '1234\5678';
WARNING: nonstandard use of escape in a string literal
LINE 1: select '1234\5678';
^
HINT:
18 matches
Mail list logo
