Re: BUG #18274: Error 'invalid XML content'

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Dmitry Koval <d(dot)koval(at)postgrespro(dot)ru>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18274: Error 'invalid XML content'
Date: 2024-01-26 01:24:07
Message-ID: ZbMJt7HRzxQ6n7j0@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, Jan 25, 2024 at 03:12:07PM +0300, Dmitry Koval wrote:
> I agree that reverting a patch is a good idea if there are concerns about
> server resources (XML is used by few users and there are even fewer users
> who need to parse elements larger than 10Mb).
> For such users it is better to create custom PostgreSQL build.

And done with f2743a7d70e7.
--
Michael

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Paquier 2024-01-26 02:51:15 Re: BUG #18310: Some SQL commands fail to process duplicate objects with error: tuple already updated by self
Previous Message jian he 2024-01-26 00:00:00 Re: [BUG] false positive in bt_index_check in case of short 4B varlena datum