The following bug has been logged online:
Bug reference: 4544
Logged by: Marcus Kempe
Email address: [EMAIL PROTECTED]
PostgreSQL version: N/A
Operating system: N/A
Description:Wiki user update error
Details:
While trying to update my user preferences in the wiki, I
John Smith wrote:
I have just run into this issue myself and I was wondering if it is
considered a bug or a missing feature?
A missing feature.
Is there a plan to address this
in an upcoming release?
Greg Stark worked on so-called "Ordered Append" patch in spring, which
would have solved
I have just run into this issue myself and I was wondering if it is
considered a bug or a missing feature? Is there a plan to address this
in an upcoming release? Has anyone found a good work around to the
problem in the interim?
Thanks!
John.
On Wed, May 7, 2008 at 4:38 AM, Marshall, Steve <[EMA
Alexandra Nitzschke <[EMAIL PROTECTED]> writes:
> Yes, its a btree.
Well, the btree code is sufficiently well tested/debugged that I think
there's zero chance of finding such a bug in it just on the suspicion
that there might be one there. We really need a test case.
rega
Yes, its a btree.
Tom Lane schrieb:
Alexandra Nitzschke <[EMAIL PROTECTED]> writes:
We have had a look at the /var/log files, no system crash, kernel panic or
messages like this has happened.
What this smells like is a failed page split --- somewhere in the index
there is a down-link pointi
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Sushil wrote:
>> *postgres: postgres testdb [local] SELECT: symbol lookup error:
>> postgres: postgres testdb [local] SELECT: undefined symbol:
>> xmlNewTextWriterMemory*
> Your problem appears to be here. Check you libxml installation. Maybe
> s
Alexandra Nitzschke <[EMAIL PROTECTED]> writes:
> We have had a look at the /var/log files, no system crash, kernel panic or
> messages like this has happened.
What this smells like is a failed page split --- somewhere in the index
there is a down-link pointing at page 77, but page 77 didn't actu
Sushil <[EMAIL PROTECTED]> writes:
> the query works on postgres 8.3 installation on a system with following
> libxml2 istalled
> libxml2-2.6.26-2.1.2
> libxml2-python-2.6.26-2.1.2
> libxml2-2.6.26-2.1.2
> its a Centos 5.1 environment.
> the system on which this issue is appearing has following
Hi,
here is some information about the server
- no other database system runs on the server
- suse 10.3, standard installation
- jvm 1.5.0_16
- as interface to the database we use jdbc version 8.1-407
- as procdural language we only use pl/pgsql
- we have no specials in the database like custom
xmlNewTextWriterMemory might be causing this issue.
I have following details in this regard.
the query works on postgres 8.3 installation on a system with following
libxml2 istalled
libxml2-2.6.26-2.1.2
libxml2-python-2.6.26-2.1.2
libxml2-2.6.26-2.1.2
its a Centos 5.1 environment.
the system
Sushil wrote:
*postgres: postgres testdb [local] SELECT: symbol lookup error:
postgres: postgres testdb [local] SELECT: undefined symbol:
xmlNewTextWriterMemory*
Your problem appears to be here. Check you libxml installation. Maybe
someone forgot to export this symbol.
--
Sent via pgsql-
11 matches
Mail list logo
