On Sun, 4 Sep 2011, Tom Lane wrote:
Jeremy Drake jere...@jdrake.com writes:
I didn't see any changes that looked like they affected
CurrentMemoryContext, but I attached the compressed context diff in case
you want to look at it.
Right now I have a feeling that this is a compiler bug.
Jeremy Drake pg...@jdrake.com writes:
On Sun, 4 Sep 2011, Tom Lane wrote:
Right now I have a feeling that this is a compiler bug.
That's my feeling, also.
Don't know
whether you have the interest/energy to try to reduce it to a reportable
test case.
If you mean reporting it to the
Hello
there is one regress test, that failed on my f14
[pavel@nemesis postgresql]$ uname -a
Linux nemesis 2.6.35.14-95.fc14.i686.PAE #1 SMP Tue Aug 16 21:12:22
UTC 2011 i686 i686 i386 GNU/Linux
regression.diffs
3676/3676 100%
***
On 09/04/2011 08:23 AM, Pavel Stehule wrote:
Hello
there is one regress test, that failed on my f14
[pavel@nemesis postgresql]$ uname -a
Linux nemesis 2.6.35.14-95.fc14.i686.PAE #1 SMP Tue Aug 16 21:12:22
UTC 2011 i686 i686 i386 GNU/Linux
regression.diffs
On 09/04/2011 08:57 AM, Andrew Dunstan wrote:
In what locale does 'sc' sort before 's4'? (And I'd humbly suggest that
whatever locale it is is possibly broken.)
EBCDIC?
Joe
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
On sön, 2011-09-04 at 08:57 -0400, Andrew Dunstan wrote:
In what locale does 'sc' sort before 's4'?
In Czech.
(And I'd humbly suggest that whatever locale it is is possibly
broken.)
There were some discussions about this in the past; it's apparently
based on a national standard and
On 09/04/2011 10:23 AM, Peter Eisentraut wrote:
On sön, 2011-09-04 at 08:57 -0400, Andrew Dunstan wrote:
In what locale does 'sc' sort before 's4'?
In Czech.
(And I'd humbly suggest that whatever locale it is is possibly
broken.)
There were some discussions about this in the past; it's
On sön, 2011-09-04 at 10:47 -0400, Andrew Dunstan wrote:
Well, I don't think we are obliged to cater for locales that break ASCII
ordering.
We do cater for that. See
commit 8cd375526790c5be8ae24c77f13ac446adda88b6
Author: Peter Eisentraut pete...@gmx.net
Date: Mon Mar 9 15:04:21 2009 +
Andrew Dunstan and...@dunslane.net writes:
On 09/04/2011 10:23 AM, Peter Eisentraut wrote:
On sön, 2011-09-04 at 08:57 -0400, Andrew Dunstan wrote:
In what locale does 'sc' sort before 's4'?
In Czech.
Well, I don't think we are obliged to cater for locales that break ASCII
ordering.
Andrew Dunstan and...@dunslane.net writes:
Well, I don't think we are obliged to cater for locales that break ASCII
ordering.
The logical conclusion of that position is that there's no need to make
the regression tests pass in any other locale than C. Which is not the
project policy, and we
On 09/04/2011 11:31 AM, Tom Lane wrote:
Andrew Dunstanand...@dunslane.net writes:
Well, I don't think we are obliged to cater for locales that break ASCII
ordering.
The logical conclusion of that position is that there's no need to make
the regression tests pass in any other locale than C.
Andrew Dunstan and...@dunslane.net writes:
On 09/04/2011 11:31 AM, Tom Lane wrote:
I think the real question that needs to be asked here is why there's not
a buildfarm member running the tests in Czech locale. And maybe some
of the other ones that have been problematic in the past. We should
On Fri, Sep 2, 2011 at 6:52 PM, Magnus Hagander mag...@hagander.net wrote:
Attached patch implements a low watermark wal location in the
walsender shmem array. Setting this value in a walsender prevents
transaction log removal prior to this point - similar to how
wal_keep_segments work,
I tried to review this patch.
It seems to me its implementation is reasonable and enough simple.
All the works of this patch is pick-up force_not_null option from
pg_attribute.attfdwoptions and transform its data structure into suitable
form to the existing BeginCopyFrom().
So, I'd almost like to
I wrote:
On a longer-term basis, I'm looking into what we could do with
extracting stats from subqueries, but that doesn't seem like material
for a backpatch. I have a draft patch that I've been playing with
(attached).
I've committed a heavily rewritten version of that patch. Git HEAD
Thanks for the review.
(2011/09/05 3:55), Kohei KaiGai wrote:
I tried to review this patch.
It seems to me its implementation is reasonable and enough simple.
All the works of this patch is pick-up force_not_null option from
pg_attribute.attfdwoptions and transform its data structure into
16 matches
Mail list logo
