The following bug has been logged on the website:

Bug reference: 7485
Logged by: Rikard Pavelic
Email address: rikard.pavelic (AT) zg (DOT) htnet.hr
PostgreSQL version: Unsupported/Unknown
Operating system: Windows
Description:

This is still an issue as reported in
http://archives.postgresql.org/pgsql...5/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


--
Sent via pgsql-bugs mailing list (pgsql-bugs (AT) postgresql (DOT) org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

On 08/08/2012 06:24 PM, rikard.pavelic (AT) zg (DOT) htnet.hr wrote:
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

--
Sent via pgsql-bugs mailing list (pgsql-bugs (AT) postgresql (DOT) org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

Argh. Disregard the version comments in my post, I totally failed to
notice the version in the subject line.

--
Craig Ringer

--
Sent via pgsql-bugs mailing list (pgsql-bugs (AT) postgresql (DOT) org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

On 8.8.2012. 13:30, Craig Ringer wrote:
SQL state: 0A000
Hint: This probably indicates that the version of libxml2 being used is not compatible with the libxml2 header files that 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.

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


--
Sent via pgsql-bugs mailing list (pgsql-bugs (AT) postgresql (DOT) org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

On 08/14/2012 11:42 PM, Rikard Pavelic wrote:
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


--
Sent via pgsql-bugs mailing list (pgsql-bugs (AT) postgresql (DOT) org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

On 15.8.2012. 3:54, Craig Ringer wrote:
PostgreSQL 9.2beta3, compiled by Visual C++ build 1600, 64-bit



--
Sent via pgsql-bugs mailing list (pgsql-bugs (AT) postgresql (DOT) org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

On Wed, Aug 15, 2012 at 2:37 PM, Rikard Pavelic
<rikard.pavelic (AT) zg (DOT) htnet.hr> wrote:
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


--
Sent via pgsql-bugs mailing list (pgsql-bugs (AT) postgresql (DOT) org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

On Wed, Aug 15, 2012 at 2:43 PM, Dave Page <dpage (AT) pgadmin (DOT) org> wrote:
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...6/msg00874.php

--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


--
Sent via pgsql-bugs mailing list (pgsql-bugs (AT) postgresql (DOT) org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

Dave Page <dpage (AT) pgadmin (DOT) org> writes:
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


--
Sent via pgsql-bugs mailing list (pgsql-bugs (AT) postgresql (DOT) org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

On Thu, Aug 16, 2012 at 3:26 PM, Tom Lane <tgl (AT) sss (DOT) pgh.pa.us> wrote:
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


--
Sent via pgsql-bugs mailing list (pgsql-bugs (AT) postgresql (DOT) org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs