[RESENDING because the attachments seems to have caused the mail to
disappear]
Oleg Kharin wrote:
Hi, Stefan
Hi Oleg!
I have readded the list and the testcases to the CC so that others can
participate in the discussion too ...
init826.sql builds necessary tables and indexes. The test quer
Tom Lane escribió:
> I wonder whether the real issue here isn't that we have some functions
> that invoke libxml without ultimately doing xmlCleanupParser() ---
> xml_in being the first obvious candidate. Maybe that is the mechanism
> through which libxml ends up with dangling pointers.
Hmm. I s
I wonder whether the real issue here isn't that we have some functions
that invoke libxml without ultimately doing xmlCleanupParser() ---
xml_in being the first obvious candidate. Maybe that is the mechanism
through which libxml ends up with dangling pointers.
regards, tom
Tom Lane escribió:
> We might be able to compromise by only resetting the context after
> an error, but this is still only possible if we have a way to make
> libxml let go of *all* pointers to alloc'd objects. I don't understand
> your comment that xmlCleanupParser solves it --- we call that alr
On 9 Jan 2008, at 23:45, Tom Lane wrote:
"Andrew Gilligan" <[EMAIL PROTECTED]> writes:
It seems there exists a bug in the way character set conversion
is handled in some circumstances.
Seems to be the bogus pfree() in pg_convert_from() that's causing
the problem :-(. Take that out and you s
"Andrew Gilligan" <[EMAIL PROTECTED]> writes:
> It seems there exists a bug in the way character set conversion
> is handled in some circumstances.
Seems to be the bogus pfree() in pg_convert_from() that's causing
the problem :-(. Take that out and you should be OK.
Thanks for the report!
On 09/01/2008, Andrew Gilligan <[EMAIL PROTECTED]> wrote:
>
> The following bug has been logged online:
>
> Bug reference: 3866
> Logged by: Andrew Gilligan
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.3RC1
> Operating system: FreeBSD 4.11
> Description:Se
Alvaro Herrera escribió:
> Tom Lane escribió:
>
> > We might be able to compromise by only resetting the context after
> > an error, but this is still only possible if we have a way to make
> > libxml let go of *all* pointers to alloc'd objects. I don't understand
> > your comment that xmlCleanup
The following bug has been logged online:
Bug reference: 3866
Logged by: Andrew Gilligan
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3RC1
Operating system: FreeBSD 4.11
Description:Segfault during table update when using convert_from()
Details:
Greetings,
Tom Lane escribió:
> We might be able to compromise by only resetting the context after
> an error, but this is still only possible if we have a way to make
> libxml let go of *all* pointers to alloc'd objects. I don't understand
> your comment that xmlCleanupParser solves it --- we call that alr
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> What problem you have with it having its own memory context? I don't
> think it has any particular disadvantage.
I don't object to that per se; I'm just saying it doesn't do much to
fix the problem. The difficulty we've got here ultimately comes down
Oleg Kharin wrote:
The following bug has been logged online:
Bug reference: 3865
Logged by: Oleg Kharin
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.6
Operating system: CentOS 5.1 x86 64-bit
Description:ERROR: failed to build any 8-way joins
Details:
A
The following bug has been logged online:
Bug reference: 3865
Logged by: Oleg Kharin
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.6
Operating system: CentOS 5.1 x86 64-bit
Description:ERROR: failed to build any 8-way joins
Details:
After PostgreSQL 8.2.5
Tom Lane escribió:
> Alvaro Herrera <[EMAIL PROTECTED]> writes:
> > What's happening is that libxml encoding handler table is being
> > allocated in an ExprContext which apparently is too short-lived.
>
> > I'm not seeing very well how to handle this -- one idea would be to
> > manually call xmlIn
Faisal N. Jawdat wrote:
> Using a Mac, so no strace. dtruss of any use?
Any luck with either dtruss or ktrace?
--
Alvaro Herrerahttp://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
---(end of broadcast)-
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> What's happening is that libxml encoding handler table is being
> allocated in an ExprContext which apparently is too short-lived.
> I'm not seeing very well how to handle this -- one idea would be to
> manually call xmlInitCharEncodingHandlers (which i
Tom Lane escribió:
> Alvaro Herrera <[EMAIL PROTECTED]> writes:
> > Hmm, what I'm seeing is that libxml is apparently trying to pfree
> > something that it didn't allocate via palloc ...
>
> Not totally surprising --- when we call xmlMemSetup() we are telling
> libxml to start using xml_palloc etc
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> Hmm, what I'm seeing is that libxml is apparently trying to pfree
> something that it didn't allocate via palloc ...
Not totally surprising --- when we call xmlMemSetup() we are telling
libxml to start using xml_palloc etc rather than its default of mal
Tom Lane escribió:
> Alvaro Herrera <[EMAIL PROTECTED]> writes:
> > I can reproduce this crash. The backtrace looks like this:
Hmm, what I'm seeing is that libxml is apparently trying to pfree
something that it didn't allocate via palloc ...
--
Alvaro Herrerahtt
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> I can reproduce this crash. The backtrace looks like this:
Ah, good. This looks like it matches a previous report, but we didn't have
a reproducible test case:
http://archives.postgresql.org/pgsql-general/2007-12/msg01086.php
Ted wrote:
The following bug has been logged online:
Bug reference: 3864
Logged by: Ted
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.6
Operating system: os x
Description:jdbc files
Details:
Sorry... I don't know where to go to find the jdbc jars.. it se
The following bug has been logged online:
Bug reference: 3864
Logged by: Ted
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.6
Operating system: os x
Description:jdbc files
Details:
Sorry... I don't know where to go to find the jdbc jars.. it seem
jdbc.pos
On 09/01/2008, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> The following bug has been logged online:
>
> Bug reference: 3863
> Logged by:
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.3 RC1
> Operating system: Windows
> Description:libpq.lib missing
> Details:
The following bug has been logged online:
Bug reference: 3863
Logged by:
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3 RC1
Operating system: Windows
Description:libpq.lib missing
Details:
Previous versions of the Postgres had libpq.lib file in $(PSQLSRC)
Sokolov Yura escribió:
> bg1.sql---
> -- crashed, when queries xmlelement with containment given by xmlagg
> -- and type of aggregated elements is different
> select xpath('any_non_empty_expression', xmlelement(name a, xmlagg(el) )) as
> el
> from ( values
> ( xmlelement(
The following bug has been logged online:
Bug reference: 3861
Logged by: Marc mamin
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.4
Operating system: Linux
Description:cannot cast type smallint to bit
Details:
Hello,
This is more a feature request than a
Sorry for previous message having no comments.
Just remark:
These aggregates created successfuly both in 8.2 and 8.3beta4:
CREATE AGGREGATE array_concat(anyarray) (
SFUNC=array_cat,
STYPE=anyarray
);
CREATE AGGREGATE array_build(anyelement) (
SFUNC=array_append,
STYPE=anyarray
);
But aggregate
The following bug has been logged online:
Bug reference: 3860
Logged by: Sokolov Yura
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3beta4
Operating system: Debian Linux 4.0r2 both 32bit and amd64
Description:xpath crashes backend when is querying xmlagg resu
Tom Lane wrote:
Joe Conway <[EMAIL PROTECTED]> writes:
Did you want me to work on this? I could probably put some time into it
this coming weekend.
I'll try to get to it before that --- if no serious bugs come up this
week, core is thinking of wrapping 8.3.0 at the end of the week, so
The following bug has been logged online:
Bug reference: 3859
Logged by: Peter Speck
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3RC1
Operating system: any
Description:version designation
Details:
Version 8.3 has huge improvements for users over 8.0/8.1/8
ktrace apparently didn't make it to osx 10.5.1. hrm. let me dig
around.
-faisal
On Jan 8, 2008, at 9:13 PM, Tom Lane wrote:
Alvaro Herrera <[EMAIL PROTECTED]> writes:
Faisal N. Jawdat wrote:
Using a Mac, so no strace. dtruss of any use?
Sure.
Or ktrace, which seems standard on my M
Using a Mac, so no strace. dtruss of any use?
-faisal
On Jan 8, 2008, at 7:03 PM, Tom Lane wrote:
Alvaro Herrera <[EMAIL PROTECTED]> writes:
Can you get a backtrace of the hung psql process?
strace'ing it up to the point of the hang might be informative too.
regard
32 matches
Mail list logo
