The following bug has been logged on the website:
Bug reference: 6334
Logged by: Wilfried Weiss
Email address: wilfried.we...@nsg.com
PostgreSQL version: 9.1.2
Operating system: AIX 5300-12-04-1119
Description:
I successfully compiled 9.1.2 using IBM xlc 9.0 and gnu m
(Horribly red face)
All my fault. It turns out I had applied a source-code change for some
additional dtracing which I had merged forward from an older version but which
was incorrect in V9. After removing that it works fine.
Really sorry about that
John Lumby
On Sun, Dec 4, 2011 at 7:27 AM, MirrorX wrote:
> hello to all,
>
> i found this error in the logs on the hot_standby server. this error
> appeared only once a few days back and hasn't come up again. the version i
> am using is 9.0.5 and the primary was loaded by restoring dump files
> (previous ve
On Fri, Dec 2, 2011 at 4:48 AM, wrote:
> The following bug has been logged on the website:
>
> Bug reference: 6317
> Logged by: hua ming fei
> Email address: h...@alkheme.com
> PostgreSQL version: 9.0.1
> Operating system: Centos 5.5
> Description:
>
> use pg_dump when didn't
On Tue, 2011-12-13 at 15:17 +, dmigow...@ikoffice.de wrote:
> The following bug has been logged on the website:
>
> Bug reference: 6333
> Logged by: Daniel Migowski
> Email address: dmigow...@ikoffice.de
> PostgreSQL version: 9.1.2
> Operating system: Windows 7
> Descripti
John Lumby writes:
> I do have other databases in my cluster which probably explains the different
> datlastsysoid.
No, it wouldn't. datlastsysoid only counts objects created during
initdb.
[ thinks for a bit ] The most likely explanation for the different
datlastsysoid value is that the numb
Yes, I'm definitely running 9.1.2 (on the output I sent earlier today).
I've also tried again on yet another different system and get the same bug
there.
I do have other databases in my cluster which probably explains the different
datlastsysoid.
I am at a loss to explain what could be differ
John Lumby writes:
> Is your output different? Do you think you could post the output you get?
Mine looks like yours, except no error. [ looks closer... ] Are you
sure you're running a 9.1.2 server? The large difference in
datlastsysoid seems like it could not have happened if you had
product
The following bug has been logged on the website:
Bug reference: 6333
Logged by: Daniel Migowski
Email address: dmigow...@ikoffice.de
PostgreSQL version: 9.1.2
Operating system: Windows 7
Description:
I have a user group "ikofficeusers", and a user "ik" in my database
Well, thanks for trying it - but that is strange. Yes, my database is
created with datcollate "C" -
the script displays that (see below).
The only thing I can think of that might explain different outcome is if, in
your environment,
the planner did not choose the index-access plan after
10 matches
Mail list logo
