On 06.03.2011 20:32, Kevin Grittner wrote:
Heikki Linnakangas wrote:
Here's what I had in mind. Can you review
The additions and modifications to the comments all look good to me.
I can see why you renamed one field and eliminated another; no
problem there. I'm really surprised, when you ig
On 08.03.2011 02:37, YAMAMOTO Takashi wrote:
The following bug has been logged online:
Bug reference: 5918
Logged by: YAMAMOTO Takashi
Email address: y...@mwd.biglobe.ne.jp
PostgreSQL version: 9.1devel
Operating system: NetBSD
Description:SummarizeOldestCommittedSxa
Hello Tom,
Now for the Problem: There is a problem with the translation of the
english word "March" to the german "März". Instead of "März" i get
"MäRz" (with uppercase "r").
You can reproduce it as follow:
# SET lc_time = "de_DE.UTF-8";
# SELECT to_char('2011-03-04 00:00:01'::date, 'TMMonth
On Tue, Mar 08, 2011 at 01:22:20PM +0200, Heikki Linnakangas wrote:
> I think we need to just treat an empty list as normal in
> SummarizeOldestcommittedSxact(), patch attached.
I just hit the same assertion. Testing this patch now.
Dan
--
Dan R. K. Ports MIT CSAIL
=?ISO-8859-15?Q?Torsten_Z=FChlsdorff?= writes:
>>> # SET lc_time = "de_DE.UTF-8";
>>> # SELECT to_char('2011-03-04 00:00:01'::date, 'TMMonth ');
>>> to_char
>>> ---
>>> MäRz 2011
>> I can reproduce the above when the database encoding is not UTF8 or
>> lc_ctype isn't a UTF8 locale.
>
Hello,
# SET lc_time = "de_DE.UTF-8";
# SELECT to_char('2011-03-04 00:00:01'::date, 'TMMonth ');
to_char
---
MäRz 2011
I can reproduce the above when the database encoding is not UTF8 or
lc_ctype isn't a UTF8 locale.
Hm... encoding of the database is UTF8. The lc_ctype is 'C'.
Looks good -- with this patch I didn't hit any assertion failures or other
errors during an hour of stress testing with DBT-2.
Dan
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
Excerpts from Euler Taveira de Oliveira's message of mar mar 08 02:06:13 -0300
2011:
> Em 07-03-2011 16:53, Owen Jacobson escreveu:
> > psql:repro.sql:2: ERROR: must be member of role "commented_role" to
> > comment upon it
> >
> This isn't a bug; let say it is a limitation (and a documented one
Alvaro Herrera writes:
> Excerpts from Euler Taveira de Oliveira's message of mar mar 08 02:06:13
> -0300 2011:
>> Em 07-03-2011 16:53, Owen Jacobson escreveu:
>>> psql:repro.sql:2: ERROR: must be member of role "commented_role" to
>>> comment upon it
>> This isn't a bug; let say it is a limita
Heikki Linnakangas wrote:
> On 08.03.2011 02:37, YAMAMOTO Takashi wrote:
>> i got the following assertion failure. given that availableList
>> is not empty and SxactGlobalXminCount == 0, i guess it was raced
>> with ReleasePredicateLocks.
>
> Yeah, that's what it looks like. One backend calls
>
On 08.03.2011 18:27, Kevin Grittner wrote:
Heikki Linnakangas wrote:
I think we need to just treat an empty list as normal in
SummarizeOldestcommittedSxact(), patch attached.
Looks good. I suggest we get that one in before the alpha is cut.
Especially since Dan was able to hit that same asse
On Wed, Feb 16, 2011 at 10:33 AM, Konrad Garus wrote:
> 2011/2/16 Tom Lane :
>> "Konrad Garus" writes:
>>> && operator seems to be broken for polygons whose bounding boxes intersect:
>>
>>> select polygon'((0,0), (1,2), (0,2))' && polygon'((0.5, 0), (1,0), (1,1))';
>>> ?column?
>>> --
>>
http://www.postgresql.org/docs/current/static/functions-geometry.html
I wish it explained what arguments each of the operators accepts, and
whether any automatic conversions take place (like polygon to box in
that 8.3 issue).
What happens when I call ?# or ?- on a polygon and point? Two points? O
I wrote:
> I thought there was nothing particularly unreasonable about Owen's
> suggestion: let users with the CREATEROLE attribute comment on any role.
> I don't think COMMENT added to CREATE ROLE would be a very nice fix
> (aside from being ugly, what if you want to change the comment later?).
>
On Tue, Mar 8, 2011 at 11:48 PM, Tom Lane wrote:
> I wrote:
>> I thought there was nothing particularly unreasonable about Owen's
>> suggestion: let users with the CREATEROLE attribute comment on any role.
>> I don't think COMMENT added to CREATE ROLE would be a very nice fix
>> (aside from being
Robert Haas writes:
> On Tue, Mar 8, 2011 at 11:48 PM, Tom Lane wrote:
>> In particular, I suggest the attached patch (code-complete, but sans
>> documentation changes).
> I think it's a good change, but we should make sure to release-note it
> properly,
I had already drafted a commit message:
16 matches
Mail list logo
