Tom Lane wrote:
> Florian Pflug writes:
> > On Jun1, 2011, at 20:28 , Peter Eisentraut wrote:
> >> Well, initdb still succeeds if you give it an invalid locale name. It
> >> warns, but that can easily be missed if initdb is hidden behind a few
> >> other layers. If you then run pg_upgrade, you g
Florian Pflug writes:
> On Jun1, 2011, at 20:28 , Peter Eisentraut wrote:
>> Well, initdb still succeeds if you give it an invalid locale name. It
>> warns, but that can easily be missed if initdb is hidden behind a few
>> other layers. If you then run pg_upgrade, you get a hosed instance.
> Wh
On Jun1, 2011, at 20:28 , Peter Eisentraut wrote:
> Well, initdb still succeeds if you give it an invalid locale name. It
> warns, but that can easily be missed if initdb is hidden behind a few
> other layers. If you then run pg_upgrade, you get a hosed instance.
Whats the rational behind that b
On ons, 2011-06-01 at 13:21 -0400, Tom Lane wrote:
> Peter Eisentraut writes:
> >>> I think you misread what I wrote, or I misexplained it, but never
> >>> mind. Matching locale names case-insensitively sounds reasonable to
> >>> me, unless someone has reason to believe it will blow up.
>
> > On
Peter Eisentraut writes:
>>> I think you misread what I wrote, or I misexplained it, but never
>>> mind. Matching locale names case-insensitively sounds reasonable to
>>> me, unless someone has reason to believe it will blow up.
> On FreeBSD, locale names appear to be case-sensitive:
> $ LC_ALL
On tis, 2011-05-24 at 15:59 -0400, Bruce Momjian wrote:
> > I think you misread what I wrote, or I misexplained it, but never
> > mind. Matching locale names case-insensitively sounds reasonable to
> > me, unless someone has reason to believe it will blow up.
>
> OK, that's what I needed to hear.
> I thought the problem was that they upgraded the OS and now the encoding
> names changed, though they behaved the same. Is that now what is
> happening? Can they supply the values with different cases?
>
In my case I never touched the locale. It was set by the OS. I presume
this is true for m
Tom Lane wrote:
> Robert Haas writes:
> > On Wed, May 25, 2011 at 2:13 PM, Bruce Momjian wrote:
> >> I thought the problem was that they upgraded the OS and now the encoding
> >> names changed, though they behaved the same. ?Is that now what is
> >> happening? ?Can they supply the values with dif
Robert Haas writes:
> On Wed, May 25, 2011 at 2:13 PM, Bruce Momjian wrote:
>> I thought the problem was that they upgraded the OS and now the encoding
>> names changed, though they behaved the same. Is that now what is
>> happening? Can they supply the values with different cases?
> Oh, hmm.
On Wed, May 25, 2011 at 2:13 PM, Bruce Momjian wrote:
> Alvaro Herrera wrote:
>> Excerpts from Robert Haas's message of mié may 25 13:33:41 -0400 2011:
>> > On Wed, May 25, 2011 at 1:22 PM, Bruce Momjian wrote:
>>
>> > > I can easily remove dashes before the compare if people like that idea
>> >
Alvaro Herrera wrote:
> Excerpts from Robert Haas's message of mi?? may 25 13:33:41 -0400 2011:
> > On Wed, May 25, 2011 at 1:22 PM, Bruce Momjian wrote:
>
> > > I can easily remove dashes before the compare if people like that idea
> > > --- I think you could argue that a dash is not significant
Excerpts from Robert Haas's message of mié may 25 13:33:41 -0400 2011:
> On Wed, May 25, 2011 at 1:22 PM, Bruce Momjian wrote:
> > I can easily remove dashes before the compare if people like that idea
> > --- I think you could argue that a dash is not significant, unless "ab-c"
> > and "a-bc" ar
On Wed, May 25, 2011 at 1:22 PM, Bruce Momjian wrote:
> Alvaro Herrera wrote:
>> Excerpts from Bruce Momjian's message of mar may 24 15:59:59 -0400 2011:
>>
>> > > I think you misread what I wrote, or I misexplained it, but never
>> > > mind. Matching locale names case-insensitively sounds reason
Alvaro Herrera wrote:
> Excerpts from Bruce Momjian's message of mar may 24 15:59:59 -0400 2011:
>
> > > I think you misread what I wrote, or I misexplained it, but never
> > > mind. Matching locale names case-insensitively sounds reasonable to
> > > me, unless someone has reason to believe it wi
Excerpts from Bruce Momjian's message of mar may 24 15:59:59 -0400 2011:
> > I think you misread what I wrote, or I misexplained it, but never
> > mind. Matching locale names case-insensitively sounds reasonable to
> > me, unless someone has reason to believe it will blow up.
>
> OK, that's what
Robert Haas wrote:
> On Mon, May 23, 2011 at 2:57 PM, Bruce Momjian wrote:
> > Robert Haas wrote:
> >> On Mon, May 23, 2011 at 8:26 AM, Bruce Momjian wrote:
> >> > Sorry, I was unclear. ?The question is whether the case of _name_ of the
> >> > locale is significant, meaning can you have two local
Robert Haas wrote:
> On Mon, May 23, 2011 at 8:26 AM, Bruce Momjian wrote:
> > Sorry, I was unclear. ?The question is whether the case of _name_ of the
> > locale is significant, meaning can you have two locale names that differ
> > only by case and behave differently?
>
> That would seem surpris
On Mon, May 23, 2011 at 2:57 PM, Bruce Momjian wrote:
> Robert Haas wrote:
>> On Mon, May 23, 2011 at 8:26 AM, Bruce Momjian wrote:
>> > Sorry, I was unclear. ?The question is whether the case of _name_ of the
>> > locale is significant, meaning can you have two locale names that differ
>> > only
On Mon, May 23, 2011 at 8:26 AM, Bruce Momjian wrote:
> Sorry, I was unclear. The question is whether the case of _name_ of the
> locale is significant, meaning can you have two locale names that differ
> only by case and behave differently?
That would seem surprising to me, but I really have no
Robert Haas wrote:
> On Sun, May 22, 2011 at 9:39 PM, Bruce Momjian wrote:
> > Tim Uckun wrote:
> >> pg_upgrade from 8.4 to 9.0 fails with the following error message.
> >>
> >> old and new cluster lc_collate values do not match
> >>
> >>
> >> on 8.4 show lc_collate outputs
> >>
> >>
On Sun, May 22, 2011 at 9:39 PM, Bruce Momjian wrote:
> Tim Uckun wrote:
>> pg_upgrade from 8.4 to 9.0 fails with the following error message.
>>
>> old and new cluster lc_collate values do not match
>>
>>
>> on 8.4 show lc_collate outputs
>>
>> en_NZ.utf8
>> (1 row)
>>
>>
>> on 9.0
Tim Uckun wrote:
> pg_upgrade from 8.4 to 9.0 fails with the following error message.
>
> old and new cluster lc_collate values do not match
>
>
> on 8.4 show lc_collate outputs
>
> en_NZ.utf8
> (1 row)
>
>
> on 9.0 it outputs
>
> en_NZ.UTF8
> (1 row)
>
>
> So the
22 matches
Mail list logo
