Re: How do you handle shared memory corruption issues? (contrib/xml2)

I compiled the libraries from the source tarballs.... I configured using --with-crypt --with-debugger --with-python. It is always possible I missed something!

Do you think the RPMs will even be applicable considering I'm not using RedHat or Fedora?

----- Original Message ----
From: Martin Gainty <mgainty(at)hotmail(dot)com>
To: CG <cgg007(at)yahoo(dot)com>; postgresql listserv <pgsql-general(at)postgresql(dot)org>
Sent: Wednesday, June 27, 2007 12:46:59 PM
Subject: Re: [GENERAL] How do you handle shared memory corruption issues? (contrib/xml2)

Hi CG

looks as if your 64bit box needs 64bit libraries instead of default 32 bit

did you check here
http://dries.studentenweb.org/apt/packages/perl-XML-LibXSLT/info.html

Let us know
M--

This email message and any files transmitted with it contain confidential
information intended only for the person(s) to whom this email message is
addressed. If you have received this email message in error, please notify
the sender immediately by telephone or email and destroy the original
message without making a copy. Thank you.

----- Original Message -----
From: "CG" <cgg007(at)yahoo(dot)com>
To: "postgresql listserv" <pgsql-general(at)postgresql(dot)org>
Sent: Wednesday, June 27, 2007 12:02 PM
Subject: [GENERAL] How do you handle shared memory corruption issues?
(contrib/xml2)

> Postgresql 8.1
>
> I made a simple modification to contrib/xml2 to include the ability to
> process exslt tags... On the production side, the postmaster crashes when
> I try to process my exslt stylesheet. On my development machine,
> everything runs without crashing. There's a number of differences there...
> There's little or no load. It has far less memory, and its PostgreSQL
> memory configuration reflects that. It has a different processor (P4
> versus x86_64 on production). There are other differences at the compiler
> and library level I'm sure. Any of these things could be contributing to
> the crashes.
>
> They are both using the same version of PsotgreSQL, compiled with the same
> options. They are both using the same version of libxml2 and libxslt.
>
> Incidently, I installed the Perl bindings for libxml2 and libxslt. I
> created a plperlu function which uses those libraries to do the xml
> transformations. It blows up in the same way.
>
> So, I suspect that there is an issue with libxslt, but I have no idea how
> to nail it down. Please advise...
>
> I'm up against a deadline, so my main goal is to get this working.
> Timelines and paychecks being as they are, I'm not nearly as concerned
> about fixing the larger problem. Is there a different way to process xml
> and (e)xslt at the database not using contrib/xml2 or XML::LibXSLT ?
>
>
>
> ____________________________________________________________________________________
> Boardwalk for $500? In 2007? Ha! Play Monopoly Here and Now (it's updated
> for today's economy) at Yahoo! Games.
> http://get.games.yahoo.com/proddesc?gamekey=monopolyherenow
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
>

____________________________________________________________________________________
TV dinner still cooling?
Check out "Tonight's Picks" on Yahoo! TV.
http://tv.yahoo.com/