Обсуждение: 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, thepostmaster 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 memoryconfiguration reflects that. It has a different processor (P4 versus x86_64 on production). There are other differencesat 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 versionof libxml2 and libxslt. Incidently, I installed the Perl bindings for libxml2 and libxslt. I created a plperlu function which uses those librariesto 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 nearlyas concerned about fixing the larger problem. Is there a different way to process xml and (e)xslt at the database notusing 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
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@yahoo.com> To: "postgresql listserv" <pgsql-general@postgresql.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 >
I compiled the libraries from the source tarballs.... I configured using --with-crypt --with-debugger --with-python. It isalways 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@hotmail.com> To: CG <cgg007@yahoo.com>; postgresql listserv <pgsql-general@postgresql.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@yahoo.com> To: "postgresql listserv" <pgsql-general@postgresql.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/
yes..go with the specific distro for your OS (either RH or Fedora) keep us apprised! Thanks/ 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@yahoo.com> To: "Martin Gainty" <mgainty@hotmail.com>; "postgresql listserv" <pgsql-general@postgresql.org> Sent: Wednesday, June 27, 2007 2:14 PM Subject: Re: [GENERAL] 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@hotmail.com> > To: CG <cgg007@yahoo.com>; postgresql listserv > <pgsql-general@postgresql.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@yahoo.com> > To: "postgresql listserv" <pgsql-general@postgresql.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/ > > ---------------------------(end of broadcast)--------------------------- > TIP 4: Have you searched our list archives? > > http://archives.postgresql.org/ >
...As we continue through this process I just want to express my sincere thanks for your suggestions heretofore....
I use neither RedHat nor Fedora :( I also didn't look carefully at the RPMs you were offering me. They are for
XML::LibXSLT,not LibXSLT. Sorry about that!
I originally built XML::LibXSLT using CPAN. For argument's sake, I dropped in just the binary from the Fedora Core 6
x86_64RPM (the rest of the RPM's contents according to diff were identical). It blew up with a Floating Point Error
whenI ran
#!/usr/bin/perl
use XML::LibXSLT;
use XML::LibXML;
my $parser = XML::LibXML->new();
my $xslt = XML::LibXSLT->new();
my $source = $parser->parse_file('foo.xml');
my $style_doc = $parser->parse_file('bar.xsl');
my $stylesheet = $xslt->parse_stylesheet($style_doc);
my $results = $stylesheet->transform($source);
print $stylesheet->output_string($results);
The auto/XML/LibXSLT/LibXSLT.so library compiled on the machine which it is running should be sufficient, right?
----- Original Message ----
From: Martin Gainty <mgainty@hotmail.com>
To: CG <cgg007@yahoo.com>; postgresql listserv <pgsql-general@postgresql.org>
Sent: Wednesday, June 27, 2007 2:23:37 PM
Subject: Re: [GENERAL] How do you handle shared memory corruption issues? (contrib/xml2)
yes..go with the specific distro for your OS (either RH or Fedora)
keep us apprised!
Thanks/
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@yahoo.com>
To: "Martin Gainty" <mgainty@hotmail.com>; "postgresql listserv"
<pgsql-general@postgresql.org>
Sent: Wednesday, June 27, 2007 2:14 PM
Subject: Re: [GENERAL] 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@hotmail.com>
> To: CG <cgg007@yahoo.com>; postgresql listserv
> <pgsql-general@postgresql.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@yahoo.com>
> To: "postgresql listserv" <pgsql-general@postgresql.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/
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
> http://archives.postgresql.org/
>
---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?
http://archives.postgresql.org/
____________________________________________________________________________________
Expecting? Get great news right away with email Auto-Check.
Try the Yahoo! Mail Beta.
http://advision.webevents.yahoo.com/mailbeta/newmail_tools.html