Thread: BUG #7485: 9.2 beta3 libxml2 can't be loaded on Windows
The following bug has been logged on the website: Bug reference: 7485 Logged by: Rikard Pavelic Email address: rikard.pavelic@zg.htnet.hr PostgreSQL version: Unsupported/Unknown Operating system: Windows Description:=20=20=20=20=20=20=20=20 This is still an issue as reported in=20 http://archives.postgresql.org/pgsql-bugs/2012-05/msg00231.php While on topic of XML is there any workaround for this? CREATE TABLE data (id int, x xml); SELECT t FROM data t GROUP BY t; I'm not really sure what operator to create. I'm fine with xml being compared like text
On 08/08/2012 06:24 PM, rikard.pavelic@zg.htnet.hr wrote: > The following bug has been logged on the website: > > Bug reference: 7485 > Logged by: Rikard Pavelic > Email address: rikard.pavelic@zg.htnet.hr > PostgreSQL version: Unsupported/Unknown > Operating system: Windows > Description: > > This is still an issue as reported in > http://archives.postgresql.org/pgsql-bugs/2012-05/msg00231.php > > While on topic of XML is there any workaround for this? > CREATE TABLE data (id int, x xml); > SELECT t FROM data t GROUP BY t; > > I'm not really sure what operator to create. I'm fine with xml being > compared like text Your report confuses me somewhat. You've linked to an issue that is extremely specific to one particular PostgreSQL version without providing the version you are using or details about your OS. You then mention the need to create an operator, which seems to have nothing to do with the problem you linked to. Please follow up with: - Your PostgreSQL version - How you installed PostgeSQL (ie the EnterpriseDB installer, from source, .zip install) - The error message you are getting and the command(s) that cause it - A description of the problem you are having -- Craig Ringer
Argh. Disregard the version comments in my post, I totally failed to notice the version in the subject line. -- Craig Ringer
On 8.8.2012. 13:30, Craig Ringer wrote: > On 08/08/2012 06:24 PM, rikard.pavelic@zg.htnet.hr wrote: >> The following bug has been logged on the website: >> >> Bug reference: 7485 >> Logged by: Rikard Pavelic >> Email address: rikard.pavelic@zg.htnet.hr >> PostgreSQL version: Unsupported/Unknown >> Operating system: Windows >> Description: >> >> This is still an issue as reported in >> http://archives.postgresql.org/pgsql-bugs/2012-05/msg00231.php >> >> While on topic of XML is there any workaround for this? >> CREATE TABLE data (id int, x xml); >> SELECT t FROM data t GROUP BY t; >> >> I'm not really sure what operator to create. I'm fine with xml being >> compared like text > Your report confuses me somewhat. You've linked to an issue that is extremely specific to one particular PostgreSQL versionwithout providing the version you are using or details about your OS. You > then mention the need to create an operator, which seems to have nothing to do with the problem you linked to. > > Please follow up with: > > - Your PostgreSQL version I've put it in the subject, because version selector didn't have it (9.2 beta3) > - How you installed PostgeSQL (ie the EnterpriseDB installer, from source, .zip install) I've used EnterpriseDB installer (9.2 beta2 with this bug, and now 9.2 beta3) > - The error message you are getting and the command(s) that cause it ERROR: could not set up XML error handler SQL state: 0A000 Hint: This probably indicates that the version of libxml2 being used is not compatible with the libxml2 header files thatPostgreSQL was built with. I'm calling function with type that has an XML attribute. I can provide a test case, but since this is just a warning of the old bug I didn't. > - A description of the problem you are having It doesn't work :D The other question I asked should probably be a second bug report, but I tried and failed to squeeze it into this one ;( Regards, Rikard
On 08/14/2012 11:42 PM, Rikard Pavelic wrote: > On 8.8.2012. 13:30, Craig Ringer wrote: >> On 08/08/2012 06:24 PM, rikard.pavelic@zg.htnet.hr wrote: >>> The following bug has been logged on the website: >>> >>> Bug reference: 7485 >>> Logged by: Rikard Pavelic >>> Email address: rikard.pavelic@zg.htnet.hr >>> PostgreSQL version: 9.2 beta3 >>> Operating system: Windows >>> Description: >>> >>> This is still an issue as reported in >>> http://archives.postgresql.org/pgsql-bugs/2012-05/msg00231.php >> - How you installed PostgeSQL (ie the EnterpriseDB installer, from source, .zip install) > I've used EnterpriseDB installer (9.2 beta2 with this bug, and now 9.2 beta3) >> - The error message you are getting and the command(s) that cause it > ERROR: could not set up XML error handler > SQL state: 0A000 > Hint: This probably indicates that the version of libxml2 being used is not compatible with the libxml2 header files thatPostgreSQL was built with. > I'm calling function with type that has an XML attribute. > I can provide a test case, but since this is just a warning of the old bug I didn't. OK, I get you. Given the context of the old report this sounds like it could be an installation/packaging issue. I'll ping the EDB folks. Which Windows is it exactly? And did you use the 32-bit or 64-bit installer? -- Craig Ringer
On 15.8.2012. 3:54, Craig Ringer wrote: > On 08/14/2012 11:42 PM, Rikard Pavelic wrote: >> On 8.8.2012. 13:30, Craig Ringer wrote: >>> On 08/08/2012 06:24 PM, rikard.pavelic@zg.htnet.hr wrote: >>>> The following bug has been logged on the website: >>>> >>>> Bug reference: 7485 >>>> Logged by: Rikard Pavelic >>>> Email address: rikard.pavelic@zg.htnet.hr >>>> PostgreSQL version: 9.2 beta3 >>>> Operating system: Windows >>>> Description: >>>> >>>> This is still an issue as reported in >>>> http://archives.postgresql.org/pgsql-bugs/2012-05/msg00231.php > >>> - How you installed PostgeSQL (ie the EnterpriseDB installer, from source, .zip install) >> I've used EnterpriseDB installer (9.2 beta2 with this bug, and now 9.2 beta3) > >>> - The error message you are getting and the command(s) that cause it >> ERROR: could not set up XML error handler >> SQL state: 0A000 >> Hint: This probably indicates that the version of libxml2 being used is not compatible with the libxml2 header files thatPostgreSQL was built with. >> I'm calling function with type that has an XML attribute. >> I can provide a test case, but since this is just a warning of the old bug I didn't. > > OK, I get you. > > Given the context of the old report this sounds like it could be an installation/packaging issue. I'll ping the EDB folks. > > Which Windows is it exactly? And did you use the 32-bit or 64-bit installer? > > -- > Craig Ringer > Windows 7 64bit PostgreSQL 9.2beta3, compiled by Visual C++ build 1600, 64-bit
On Wed, Aug 15, 2012 at 2:37 PM, Rikard Pavelic <rikard.pavelic@zg.htnet.hr> wrote: > On 15.8.2012. 3:54, Craig Ringer wrote: >> On 08/14/2012 11:42 PM, Rikard Pavelic wrote: >>> On 8.8.2012. 13:30, Craig Ringer wrote: >>>> On 08/08/2012 06:24 PM, rikard.pavelic@zg.htnet.hr wrote: >>>>> The following bug has been logged on the website: >>>>> >>>>> Bug reference: 7485 >>>>> Logged by: Rikard Pavelic >>>>> Email address: rikard.pavelic@zg.htnet.hr >>>>> PostgreSQL version: 9.2 beta3 >>>>> Operating system: Windows >>>>> Description: >>>>> >>>>> This is still an issue as reported in >>>>> http://archives.postgresql.org/pgsql-bugs/2012-05/msg00231.php >> >>>> - How you installed PostgeSQL (ie the EnterpriseDB installer, from source, .zip install) >>> I've used EnterpriseDB installer (9.2 beta2 with this bug, and now 9.2 beta3) >> >>>> - The error message you are getting and the command(s) that cause it >>> ERROR: could not set up XML error handler >>> SQL state: 0A000 >>> Hint: This probably indicates that the version of libxml2 being used is not compatible with the libxml2 header filesthat PostgreSQL was built with. >>> I'm calling function with type that has an XML attribute. >>> I can provide a test case, but since this is just a warning of the old bug I didn't. >> >> OK, I get you. >> >> Given the context of the old report this sounds like it could be an installation/packaging issue. I'll ping the EDB folks. >> >> Which Windows is it exactly? And did you use the 32-bit or 64-bit installer? >> >> -- >> Craig Ringer >> > Windows 7 64bit > PostgreSQL 9.2beta3, compiled by Visual C++ build 1600, 64-bit > This still seems to be an issue in the test beta4 installers rolled this morning. I'm looking into it. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
On Wed, Aug 15, 2012 at 2:43 PM, Dave Page <dpage@pgadmin.org> wrote: > On Wed, Aug 15, 2012 at 2:37 PM, Rikard Pavelic > <rikard.pavelic@zg.htnet.hr> wrote: >> On 15.8.2012. 3:54, Craig Ringer wrote: >>> On 08/14/2012 11:42 PM, Rikard Pavelic wrote: >>>> On 8.8.2012. 13:30, Craig Ringer wrote: >>>>> On 08/08/2012 06:24 PM, rikard.pavelic@zg.htnet.hr wrote: >>>>>> The following bug has been logged on the website: >>>>>> >>>>>> Bug reference: 7485 >>>>>> Logged by: Rikard Pavelic >>>>>> Email address: rikard.pavelic@zg.htnet.hr >>>>>> PostgreSQL version: 9.2 beta3 >>>>>> Operating system: Windows >>>>>> Description: >>>>>> >>>>>> This is still an issue as reported in >>>>>> http://archives.postgresql.org/pgsql-bugs/2012-05/msg00231.php >>> >>>>> - How you installed PostgeSQL (ie the EnterpriseDB installer, from source, .zip install) >>>> I've used EnterpriseDB installer (9.2 beta2 with this bug, and now 9.2 beta3) >>> >>>>> - The error message you are getting and the command(s) that cause it >>>> ERROR: could not set up XML error handler >>>> SQL state: 0A000 >>>> Hint: This probably indicates that the version of libxml2 being used is not compatible with the libxml2 header filesthat PostgreSQL was built with. >>>> I'm calling function with type that has an XML attribute. >>>> I can provide a test case, but since this is just a warning of the old bug I didn't. >>> >>> OK, I get you. >>> >>> Given the context of the old report this sounds like it could be an installation/packaging issue. I'll ping the EDB folks. >>> >>> Which Windows is it exactly? And did you use the 32-bit or 64-bit installer? >>> >>> -- >>> Craig Ringer >>> >> Windows 7 64bit >> PostgreSQL 9.2beta3, compiled by Visual C++ build 1600, 64-bit >> > > This still seems to be an issue in the test beta4 installers rolled > this morning. I'm looking into it. So Sachin and I have looked at this but not found a problem with the installers. He then found that one of our colleagues has already reported this as an issue with PostgreSQL and submitted a possible patch. So, we need a committer to look at fixing this: http://archives.postgresql.org/pgsql-hackers/2012-06/msg00874.php -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Dave Page <dpage@pgadmin.org> writes: > So Sachin and I have looked at this but not found a problem with the > installers. He then found that one of our colleagues has already > reported this as an issue with PostgreSQL and submitted a possible > patch. So, we need a committer to look at fixing this: > http://archives.postgresql.org/pgsql-hackers/2012-06/msg00874.php Seems pretty brute-force. Why not just #if LIBXML_VERSION > 20703 #define HAVE_XMLSTRUCTUREDERRORCONTEXT #endif in some suitable place (probably xml.c itself, since I don't think we want to #include xmlversion.h in global headers)? Or actually, maybe we could just unconditionally define HAVE_XMLSTRUCTUREDERRORCONTEXT in pg_config.h.win32. Is anybody likely to still be building PG with ancient libxml on Windows? regards, tom lane
On Thu, Aug 16, 2012 at 3:26 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > Dave Page <dpage@pgadmin.org> writes: >> So Sachin and I have looked at this but not found a problem with the >> installers. He then found that one of our colleagues has already >> reported this as an issue with PostgreSQL and submitted a possible >> patch. So, we need a committer to look at fixing this: > >> http://archives.postgresql.org/pgsql-hackers/2012-06/msg00874.php > > Seems pretty brute-force. Why not just > > #if LIBXML_VERSION > 20703 > #define HAVE_XMLSTRUCTUREDERRORCONTEXT > #endif > > in some suitable place (probably xml.c itself, since I don't think we > want to #include xmlversion.h in global headers)? > > Or actually, maybe we could just unconditionally define > HAVE_XMLSTRUCTUREDERRORCONTEXT in pg_config.h.win32. Is anybody > likely to still be building PG with ancient libxml on Windows? That works for me. Using older libxml's would be a bad idea anyway - and there are precompiled binaries available, so it's not hard to get. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
On Thu, Aug 16, 2012 at 3:28 PM, Dave Page <dpage@pgadmin.org> wrote: > On Thu, Aug 16, 2012 at 3:26 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote: >> Dave Page <dpage@pgadmin.org> writes: >>> So Sachin and I have looked at this but not found a problem with the >>> installers. He then found that one of our colleagues has already >>> reported this as an issue with PostgreSQL and submitted a possible >>> patch. So, we need a committer to look at fixing this: >> >>> http://archives.postgresql.org/pgsql-hackers/2012-06/msg00874.php >> >> Seems pretty brute-force. Why not just >> >> #if LIBXML_VERSION > 20703 >> #define HAVE_XMLSTRUCTUREDERRORCONTEXT >> #endif >> >> in some suitable place (probably xml.c itself, since I don't think we >> want to #include xmlversion.h in global headers)? >> >> Or actually, maybe we could just unconditionally define >> HAVE_XMLSTRUCTUREDERRORCONTEXT in pg_config.h.win32. Is anybody >> likely to still be building PG with ancient libxml on Windows? > > That works for me. Using older libxml's would be a bad idea anyway - > and there are precompiled binaries available, so it's not hard to get. Works as in, I'm happy with it. I haven't tested. Though, it'll likely break some of the old BF animals (temporarily, I hope). -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Dave Page <dpage@pgadmin.org> writes:
> On Thu, Aug 16, 2012 at 3:28 PM, Dave Page <dpage@pgadmin.org> wrote:
>> On Thu, Aug 16, 2012 at 3:26 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>> Seems pretty brute-force. Why not just
>>>
>>> #if LIBXML_VERSION > 20703
>>> #define HAVE_XMLSTRUCTUREDERRORCONTEXT
>>> #endif
>>>
>>> in some suitable place (probably xml.c itself, since I don't think we
>>> want to #include xmlversion.h in global headers)?
>>>
>>> Or actually, maybe we could just unconditionally define
>>> HAVE_XMLSTRUCTUREDERRORCONTEXT in pg_config.h.win32. Is anybody
>>> likely to still be building PG with ancient libxml on Windows?
>> That works for me. Using older libxml's would be a bad idea anyway -
>> and there are precompiled binaries available, so it's not hard to get.
> Works as in, I'm happy with it. I haven't tested. Though, it'll likely
> break some of the old BF animals (temporarily, I hope).
On the whole plan A sounds safer (ie look at LIBXML_VERSION in place of
using a configure test). I'll work on that tonight or tomorrow, if
nobody beats me to it.
regards, tom lane