> > I'm currently without real access to a 64bit system until I come back home.
> > If
> > it is 64bit on *all* 64bit systems the problem is slightly different.
Just committed a patch to HEAD that hopefully fixes the problem.
Michael
--
Michael Meskes
Michael at Fam-Meskes dot De, Michael at
"KOIZUMI Satoru" writes:
> "lo_compat_privileges configuration parameter , Previous PostgreSQL
> Versions" is classified into "Symbols" at index of PostgreSQL 9.0beta1
> Documentation. It would be classified into "L".
Fixed, thanks. Apparently is sensitive to contained white
space, which seems
Krzysztof Nienartowicz writes:
> surveys-> SELECT t1.SURVEY_PK, t1.SOURCE_PK, t1.TSTYPE, t1.VALS
> surveys-> FROM sources t0 ,TS t1 where
> surveys-> (t0.SURVEYID = 16 AND t0.SRCID >= 203510110032281 AND
> t0.SRCID <= 203520107001677 and t0.SURVEYID = t1.SURVEY_PK AND t0.SRCID =
> t1.SOURCE_
Hello,
Sorry for the re-post - not sure list is the relevant one, I included
slightly changed query in the previous message, sent to bugs list.
I have an ORM-generated queries where parent table keys are used to
fetch the records from the child table (with relevant FK indicies),
where child tabl
Hello,
I have an ORM-generated queries where parent table keys are used to
fetch the records from the child table (with relevant FK indicies),
where child table is partitioned. My understanding is that Postgres is
unable to properly use constraint exclusion to query only a relevant
table? Half of t
2010/5/20 Diffor
> December 2009 cumulative time zone update for Microsoft Windows operating
> systems:
> http://support.microsoft.com/?kbid=976098
>
> pgtz.c is outdated:
> >N. Central Asia Standard Time:
> >Removes “Almaty” from the “(GMT+06:00) Almaty, Novosibirsk” time zone.
>
I contact peop
The following bug has been logged online:
Bug reference: 5467
Logged by: KOIZUMI Satoru
Email address: koizumi...@minos.ocn.ne.jp
PostgreSQL version: 9.0beta1
Operating system: MacOS X
Description:wrong classification at index
Details:
"lo_compat_privileges configur
Ah, good reference - thanks for digging that up. Interstingly enough
they seem to have just removed Almaty - and not put it anywhere else
:-)
But as someone said, they're being screwed, but only by MS, not us.
I've applied the change to pgtz.c. It will be in the next releases.
//Magnus
On Thu,
December 2009 cumulative time zone update for Microsoft Windows operating
systems:
http://support.microsoft.com/?kbid=976098
pgtz.c is outdated:
>N. Central Asia Standard Time:
>Removes “Almaty” from the “(GMT+06:00) Almaty, Novosibirsk” time zone.
