Issue: Deprecation of the XML2 module 'xml_is_well_formed'function Robert Haas wrote: On Mon, Jun 28, 2010 at 11:42 AM, Mike Rylander <mrylander(a)gmail.com> wrote: You could do something like this (untested): CREATE OR REPLACE FUNCTION my_xml_is_valid ( x TEXT ) RETURNS BOOL AS $$ BEGIN PERFORM XMLPARSE( DOCUMENT x::XML ); RETURN TRUE; EXCEPTION W... 28 Jun 2010 12:50
Issue: Deprecation of the XML2 module'xml_is_well_formed' function On Mon, Jun 28, 2010 at 08:08:53AM -0700, Mike Berrow wrote: We need to make extensive use of the 'xml_is_well_formed' function provided by the XML2 module. Yet the documentation says that the xml2 module will be deprecated since "XML syntax checking and XPath queries" is covered by the XML-related f... 9 Jul 2010 17:13
Issue: Deprecation of the XML2 module 'xml_is_well_formed' function On Mon, Jun 28, 2010 at 11:08 AM, Mike Berrow <mberrow(a)gmail.com> wrote: We need to make extensive use of the 'xml_is_well_formed' function provided by the XML2 module. Yet the documentation says that the xml2 module will be deprecated since "XML syntax checking and XPath queries" is covered by the XML-r... 12 Jul 2010 08:30
[HACKERS] Built-in connection pool The thread on Admission Control caused me to realize that one policy I'd been considering as a possibly useful second tier (execution) admission control policy was actually more appropriate as a first tier (simple) admission control policy. The difference (as defined in the Hellerstein, Stonebraker & Hamilton pape... 28 Jun 2010 11:43
[HACKERS] Issue: Deprecation of the XML2 module 'xml_is_well_formed' function We need to make extensive use of the 'xml_is_well_formed' function provided by the XML2 module. Yet the documentation says that the xml2 module will be deprecated since "XML syntax checking and XPath queries" is covered by the XML-related functionality based on the SQL/XML standard in the core server from Postgr... 28 Jun 2010 11:43
suppress automatic recovery after back crash Robert Haas <robertmhaas(a)gmail.com> writes: On Thu, Jun 17, 2010 at 7:25 PM, Tom Lane <tgl(a)sss.pgh.pa.us> wrote: Then all you need is a tweak to make the postmaster exit(1) after a crash instead of trying to launch recovery. This seems useful to me so here's a patch to implement it. Hm, is it useful ... 19 Jul 2010 21:17
[HACKERS] suppress automatic recovery after back crash [moving from -performance to -hackers; original subject is: PostgreSQL as a local in-memory cache] On Thu, Jun 17, 2010 at 7:25 PM, Tom Lane <tgl(a)sss.pgh.pa.us> wrote: Josh Berkus <josh(a)agliodbs.com> writes: (a) and (d) are probably simple, if by "reprovisioning" you mean "rm -rf $PGDATA; initdb". ... 27 Jun 2010 21:36
pg_dump's checkSeek() seems inadequate I wrote: The test that checkSeek() is using is to see whether this works: fseeko(fp, 0, SEEK_CUR) and apparently on this platform that's a no-op even on an otherwise unseekable file. BTW, I looked in the archives for related discussions and found only the thread in which the current fseek-checking code... 28 Jun 2010 11:43
[HACKERS] pg_dump's checkSeek() seems inadequate While testing a fix for the pg_restore issues mentioned a few days ago, I noticed that checkSeek() returns true on my old HPUX box even when the input is in fact not seekable, for instance a pipe. This leads to pg_restore failing completely in cases where it ought to work, like this: $ cat vector.dump | pg_resto... 27 Jun 2010 13:55
Why are these modules built without respecting my LDFLAGS? "Aaron W. Swenson" <aaron.w.swenson(a)gmail.com> writes: I have a short list of modules that have been built without respecting my LDFLAGS and/or LDFLAGS_SL. It's difficult to comment on this since you haven't told us what flags you wanted to inject, nor exactly how you tried to inject them, nor what version ... 3 Jul 2010 18:59 |