Simon Riggs wrote:
On Thu, 2008-09-11 at 15:39 +0300, Peter Eisentraut wrote:
Bruce Momjian wrote:
Abhijit Menon-Sen wrote:
I thought -patches was supposed to die. What happened?
I was wondering the same thing. Peter?
Hmm, let's try this:
Anyone who thinks the patches list should r
Bruce Momjian wrote:
Abhijit Menon-Sen wrote:
I thought -patches was supposed to die. What happened?
I was wondering the same thing. Peter?
Hmm, let's try this:
Anyone who thinks the patches list should remain as separate from
hackers, shout now (with rationale)!
--
Sent via pgsql-patch
Am Freitag, 13. Juni 2008 schrieb [EMAIL PROTECTED]:
> Here is the SSL patch we discussed previously for 8.3.1.
I saw this patch in the commit fest list. I suppose this is actually intended
for 8.4, not 8.3?
--
Sent via pgsql-patches mailing list (pgsql-patches@postgresql.org)
To make changes
Am Freitag, 4. Juli 2008 schrieb Tom Raney:
> Regarding the XML datum, in order to support that, will all users need
> to compile with libxml? Are there any lighter weight solutions to
> serialize other than libxml?
You can create XML without libxml.
--
Sent via pgsql-patches mailing list (
Am Mittwoch, 2. Juli 2008 schrieb Tom Raney:
> This is an update to my EXPLAIN XML patch submitted a few days ago.
Could you explain how you came up with the XML schema design? I suppose you
just made something up that went along with the existing XML output.
I would like to see more integratio
For some experiments I wanted to run the regression tests using a different
database (possibly using pg_regress --dbname=), but the name "regression" is
hardcoded in a few places. It's trivial to fix, see attached patch. Quick
explanation: The fact that psql's \z prints the database name has a
With GCC 4.3, I get warnings from every flex scanner that 'input' is defined
but not used. This can be solved by adding %option noinput. I tested this
option with a current flex and with the old 2.5.4a; both accept it. See
attached patch. Does anyone see problems with this?
diff --git a/src/
Am Donnerstag, 8. Mai 2008 schrieb Simon Riggs:
> CREATE RULE somename AS ON INSERT TO x WHERE where-clause DO INSERT ...
>
> which seems straightforward, no?
Double evaluation is the key word. The conclusion was more or less that you
can't implement check constraints using the rules system. Y
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > I have developed the attached patch which fixes 0 ^ 123.3.
>
> Did you actually read the wikipedia entry you cited?
Considering that 0::float8 ^ 0::float8 yields 1, making the numeric operator
do the same might not be completely unre
Am Mittwoch, 7. Mai 2008 schrieb Tom Lane:
> >> 1.1 Add a column named 'attrel' in pg_attribute catalog to store
> >> column privileges. Now all column privileges are stored, no matter
> >> whether they could be implied from table-level privilege.
>
> What this actually means, but doesn't say, is t
Dave Page wrote:
> > Perhaps use a separate string for machine parse (say R, T, C, U), and
> > let the string be translatable.
>
> I considered that, but wasn't sure if folks would like the redundancy.
> It's trivial to do of course - any objections?
Is there anything useful you would do with this
Andrew Dunstan wrote:
> This patch should fix things for both sets of changes. And it
> demonstrates pretty much what you need to do for config options for MSVC.
Btw., it is quite easily possible to use the autom4te tracing facility to
parse the configure.ac file, in case you are interested in ge
Alvaro Herrera wrote:
> The developer's FAQ is supposed to contain this kind of thing, but I
> think it's rather thin on actual details. (Some time ago it was
> proposed to create a "style guide", but people here thought it was a
> waste of time and "it will not cover what's really important", so
Bruce Momjian wrote:
> I checked the use of COLUMNS and it seems bash updates the environment
> variable when a window is resized. I added ioctl(TIOCGWINSZ) if COLUMNS
> isn't set. We already had a call in print.c for detecting the
> number of rows on the screen to determine if the pager should
>
Am Donnerstag, 3. April 2008 schrieb Brendan Jurd:
> psql allows you to omit the space between the command and argument?
> Does anybody else find that weird?
> What is the virtue of allowing such a syntax in the first place?
Combatability with hysterial practice.
--
Sent via pgsql-patches mailin
Am Donnerstag, 3. April 2008 schrieb Gregory Stark:
> \old means something *today*. In the proposed syntax by creating the alias
> you're changing what it means.
Yes. There are two complementary responses to that:
1. That's an intentional, useful feature of aliases.
2. If you don't like it, don'
Am Donnerstag, 3. April 2008 schrieb Gregory Stark:
> To be more explicit what I meant was someone doing
>
> #= \alias old select version();
> ...
> #= \oldd
>
> #= \old
> #= select 'where is all my output going?'
> #= select 'what happened to my ldd file?'
This is a valid concern, but it is orth
The attached patch implements a few changes to how shared libraries and
dynamically loadable modules are built. Foremost, it creates a solid
distinction between these two types of targets based on what had already been
implemented and duplicated in ad hoc ways before. Specifically,
- Dynamica
Am Dienstag, 1. April 2008 schrieb Tom Lane:
> Do we really want such a thing?
Yes!
> The space of backslash command names
> is so densely populated already that it's hard to imagine creating
> aliases without conflicting with existing (or future) command names
> --- as indeed your example does.
Zdenek Kotala wrote:
> But how it was mentioned in this thread maybe
> somethink like this "CREATE TABLESPACE name LOCATION '/my/location'
> SEGMENTS 10GB" should good solution. If segments is not mentioned then
> default value is used.
I think you would need a tool to resegmentize a table or tabl
Am Donnerstag, 6. März 2008 schrieb Robert Lor:
> Attached is the updated patch which addressed all the concerns from
> Peter and Tom.
>
> * The header file containing the probe macros is now included only in
> the .c files that need it.
> * All probe macro names now start with TRACE_ (eg:
> TRACE_
Am Donnerstag, 6. März 2008 schrieb Tom Lane:
> I attach a proposed patch against HEAD for this. It's a bit long
> but most of the bulk is refactoring eqsel() to make it easy to use from
> prefix_selectivity(). The intellectual content is just in the last
> diff hunk.
Looking at the patch as com
ITAGAKI Takahiro wrote:
> DWORD is an alias for 'unsigned long' in 32bit Windows.
Then try using %lu and no casts. That should get rid of the warnings the
proper way.
--
Sent via pgsql-patches mailing list (pgsql-patches@postgresql.org)
To make changes to your subscription:
http://www.postgres
ITAGAKI Takahiro wrote:
> - Cast DWORD to unsigned integer explicitly.
> DWORD is always 32bit integer on both 32bit and 64bit Windows.
I think if that is so, you wouldn't need to add any casts. Instead you would
only need to use the right format specifier.
--
Sent via pgsql-patches mailin
Zdenek Kotala wrote:
> Yes, agree. It seems only ZFS is OK at this moment and if somebody sets
> 32TB he gets nonsegment mode anyway.
Surely if you set the segment size to INT64_MAX, you will get nonsegmented
behavior anyway, so two code paths might not be necessary at all.
> I looked into posix
Tom Lane wrote:
> I think this needs to be treated as experimental until it's got a few
> more than zero miles under its belt.
OK, then maybe we should document that.
> I wouldn't be too surprised to
> find that we have to implement it as a run-time switch instead of
> compile-time, in order to
Tom Lane wrote:
> Zdenek Kotala <[EMAIL PROTECTED]> writes:
> > There is latest version of nonsegment support patch. I changed
> > LET_OS_MANAGE_FILESIZE to USE_SEGMENTED_FILES and I added
> > -disable-segmented-files switch to configure. I kept tuplestore behavior
> > and it still split file in bo
Am Donnerstag, 6. März 2008 schrieb Tom Lane:
> To help out Peter's client, who's running 8.1.x, we'd have to backpatch
> at least that far. We backpatched the last round of LIKE selectivity
> fixes to 8.1, so I don't have too much hesitation about doing the same
> here.
Thanks for the offer. Pe
Am Freitag, 29. Februar 2008 schrieb Robert Lor:
> Currently, pg_trace.h is included in c.h, and I feel strongly that it
> should remains there because by design I'd like to
> 1) have the tracing feature be available both in the frontend and
> backend without having to do anything extra,
I think
Am Freitag, 29. Februar 2008 schrieb Robert Lor:
> My concern is that when we start adding more probes (not just the
> backend), we will have to add the following 5 lines in .c files that use
> the Dtrace macros.
I had already solved this in my intermediate patch I sent you by symlinking
probes_n
Robert Lor wrote:
> Please find the patch attached per this thread
> http://archives.postgresql.org/pgsql-hackers/2008-02/msg00912.php
Another thing that is concerning me about this new approach is the way the
probes are named. For example, we'd now have a call
POSTGRESQL_LWLOCK_ACQUIRE()
in t
Robert Lor wrote:
> dtrace call in src/Makefile is to generate probes.h before any file is
> compiled so it can be used in c.h to avoid "probes.h not found" error.
> The dtrace call in src/backend/Makefile is only needed for Solaris.
Is c.h the right place to include this? The probes are only in
imilar cases. This should fix the troubles you
describe and others.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
Index: src/backend/Makefile
===
RCS file: /cvsroot/pgsql/src/backend/Makefile,v
retrieving revision 1
Solaris support that
mechanism as well, so the old one could be dropped?
Btw., probes_null.h is missing in your patch.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 4: Have you searched our list archives?
mal testing the dtrace
support could be helpful. :)
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
,
stable, and standardized, export sprintf and strftime to PostgreSQL.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
Am Dienstag, 26. Februar 2008 schrieb Magne Mæhre:
> I noticed that the dtrace code wouldn't build after the recent SUBSYS.o
> reorganization.
Fixed.
Is there no buildfarm coverage of dtrace?
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---
test them. Just
see if it builds and runs correctly. Thanks.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
diff -ur ../cvs-pgsql/src/interfaces/ecpg/compatlib/Makefile ./src/interfaces/ecpg/compatlib/Makefile
--- ../cvs-pgsql/src/interfaces/ecpg/compatlib/Makefile 2008-02-17
mostly formatting and some
refactoring) and published them here:
http://git.postgresql.org/?p=~petere/postgresql.git;a=shortlog;h=avahi-support
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 6: explain analyze is your friend
lable for a wider variety of platforms.
One thing I found curious: The Bonjour code uses service
type "_postgresql._tcp." whereas your code uses "_postgresql._tcp" (note the
dot). Is that an expected difference?
--
Peter Eisentraut
http://developer.postgresql.org/~petere
erver from a set of equivalent instances. I don't see
how this can be useful in a PostgreSQL setting, at least not based on the
parameters server version and protocol version that you implemented.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
-
lp
if you could include or point to your actual patch.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
Am Freitag, 22. Februar 2008 schrieb Zdenek Kotala:
> Peter Eisentraut napsal(a):
> > Zdenek Kotala wrote:
> >> However, I get following error on Solaris:
> >>
> >> bash-3.2$ /usr/postgres/8.2/bin/postgres -D /tmp/db
> >> --share_buffers=16000 /
ut following command works fine:
>
> /usr/postgres/8.2/bin/postgres -D /tmp/db -c shared_buffers=16000
share_buffers is not the same as shared_buffers.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)--
Zdenek Kotala wrote:
> I attach fix for --help output. I replaced --NAME... with -NAME
But that is wrong.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 5: don't forget to increase your free s
should not
change any functionality of the build system at the moment.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
diff --git a/src/backend/access/Makefile b/src/backend/access/Makefile
index 4753eac..df05f8e 100644
--- a/src/backend/access/Makefile
+++ b/src/backend/access
In 8.3, it appears that NUMERIC doesn't need to be a key word any longer. See
attached patch. Was there a reason this was kept in the parser? Otherwise
we could remove it in 8.4.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
diff -ur ../cvs-pgsql/src/backend/parser/g
s can access system tables with source code
> or can use debugger).
Have you thought about a solution that applies the regular access privileges
to pg_proc in order to hide some content from less privileged users?
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
o encryption purposes would be a hazard.
PostgreSQL already has built-in support for SSL and Kerberos, so it is already
infested with enough weaponized code to fail most applicable regulations.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
-
ools is that they don't already tell you how to get
help when you log in.
Now I have actually thought for a while whether we could get rid of the login
text altogether. I would support trading that for extended help options.
But if the login note is there, then we don't need more
Greg Sabino Mullane wrote:
> Why not run help when someone enters "help" (or "HELP ME!") on the
> command line? \? is hardly an easy thing to remember (and some people
> can't be bothered to actually read the screen...)
Then surely the help output won'
nitdb.
I didn't follow how the user got into this mess, so I don't know whether the
suggestion "you need to initdb" is appropriate.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
diff -ur ../cvs-pgsql/src/backend/access/transam/xlog.c ./src/backend/access/transa
the client has a root certificate installed.
How would a client check whether the socket file is in a secure location?
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 3: Have you checked
the client to only talk to
servers that can prove their identity.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
.) Of course there also need to be prudent
users, but that is the case for any security system.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 7: You can help support the PostgreSQL project by donat
No moving
around of files by the server will ever solve the problem.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 7: You can help support the PostgreSQL project by donating at
Bruce Momjian wrote:
> I have written the following documentation addition suggesting the use
> of external_pid_file.
How does that prevent spoofing?
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP
valent to the old behavior of the Red Hat RPMs that
automatically performed initdb if the data directory is missing. Thankfully,
that has been abolished.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 2: Do
Am Freitag, 14. Dezember 2007 schrieb Bruce Momjian:
> I have applied the attached patch to give a helpful message if you try
> to create postgres.ps or postgres.pdf.
I have corrected this to use $(MAKE) instead of gmake, because the latter
might not be available.
--
Peter Eisentrau
would actually cover anything that would be valid as an HTML
tag. (As opposed to the fact that an XML document is not a superset of an
HTML document.)
SGML might be too broad. It would require us to recognize "" and "<>" and
perhaps a few other odd things.
Am Montag, 12. November 2007 schrieb Simon Riggs:
> On Mon, 2007-11-12 at 14:28 +0100, Peter Eisentraut wrote:
> > Simon Riggs wrote:
> > > I enclose 3 Dialects for PostgreSQL, as discussed on -hackers.
> >
> > There is no such thing as PostgreSQL 8. Please don&#
Simon Riggs wrote:
> I enclose 3 Dialects for PostgreSQL, as discussed on -hackers.
There is no such thing as PostgreSQL 8. Please don't do that; it would
confuse users about the versioning scheme.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---
Am Montag, 29. Oktober 2007 schrieb Magnus Hagander:
> 1) does it look ok?
yes
> 2) is it ok to put checks for win32-only this way?
Well, the available replacement implementation only works on win32, so this is
about as correct as we should care to be at the moment.
--
Peter Eisentrau
ot assume that the build environment is the same as the run
environment.
Anyway, just run make check and you will know. Anything else would be much
too complicated. This patch just provides direct access to the process that
people already use anyway.
--
Peter Eisentraut
http://developer.postg
to modify also
> pg_config to show where TZ files are stored.
pg_config --configure would show it.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
extent the regression tests exercise the specifics of the
time zone data, but when you specify something totally wrong some tests fail,
so it would be easy to catch that.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
diff -ur cvs-pgsql/configure pgsql/configure
--- cvs-pgsql/configure
Brendan Jurd wrote:
> This patch adds the default location for the DocBook DSSSL
> stylesheets in gentoo's package system to the configure script.
Uh, could you please send a diff with -u or -c, so we know where to put
the change?
--
Peter Eisentraut
http://developer.postgresql.
Am Dienstag, 24. Juli 2007 17:24 schrieb Gregory Stark:
> Can we just disable const checking for MSVCC in general without using the
> #pragmas? It clearly doesn't understand how const works making that warning
>
> >from it useless.
That was my thought.
--
P
Am Freitag, 20. Juli 2007 13:28 schrieb Patrick Welche:
> Also, why did postgresql choose not to use automake?
The was never such a choice made.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 1:
Am Mittwoch, 18. Juli 2007 17:16 schrieb Alvaro Herrera:
> Peter Eisentraut wrote:
> > Am Mittwoch, 18. Juli 2007 16:16 schrieb Tom Lane:
> > > You should *not* have to inform the machine that NULL is a pointer.
> >
> > For variadic functions, that expectation is
her.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
e
risk of a loss due to asynchronous commit happening is larger than fsync off.
I *think* I know what this is trying to say, but I suspect that the average
user might not be able to make a good choice of settings.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
is not
always a sufficient sentinel for variadic functions, as explained here:
<http://c-faq.com/null/null2.html>.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 4: Have you searched our list archives
don't think disk space is really a concern, is it?
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
Am Mittwoch, 4. Juli 2007 17:04 schrieb Zdenek Kotala:
> I attach complete patch which renames following binaries
>
> createdb createlang createuser dropdb droplang dropuser clusterdb
> vacuumdb reindexdb
I just want to say I dislike this idea.
--
Peter Eis
at this patch
addresses. (Might wanna check.) Since we're not going to put new
features into earlier releases, and contrib modules are not necessarily
source backward-compatible, I don't think this patch has a place in a
future PostgreSQL release.
--
Peter Eisentraut
http:
ing lower-case words
instead of upper case, except for it looks nicer. Is there a technical
reason?
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
r discussion.
> 6. (bugfix) Work with fragments with prologue: select xpath('/a',
> ''); // now XML datum is always wrapped
> with dummy ..., XML prologue simply goes away (if any).
> 7. Some cleanup.
Applied.
--
Peter Eisentraut
http://developer.postgresql.org/
Am Montag, 21. Mai 2007 15:21 schrieb Gregory Stark:
> Also, I forgot to mention previously there is an unrelated trivial hunk in
> here. I noticed we free the password early, presumably for security
> reasons,
No, to save memory.
--
Peter Eisentraut
http://developer.postgresql.or
Am Montag, 21. Mai 2007 00:01 schrieb Jeff Davis:
> Here is the latest version of my patch that's revised according to my
> discussions with Heikki and Simon:
This patch was apparently done against 8.2.4, but it doesn't apply to CVS
head.
--
Peter Eisentraut
http://develope
Am Montag, 14. Mai 2007 03:56 schrieb David Fetter:
> +For those things which CVS does not do
> +by itself, such as letting you create patches without write access,
I don't think that is accurate.
--
Peter Eisentraut
http://developer.postgresql.
t does this mean? Is there code that selects the second tablespace to use?
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 6: explain analyze is your friend
erday.
What I have been missing all along in these patches is an explanation for what
it means to list multiple temporary tablespaces. Are they used in order, or
the first one that exists, or what?
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
Am Freitag, 4. Mai 2007 18:21 schrieb Joachim Wieland:
> The appended patch addresses the outstanding issues of the recent guc
> patch. It makes PGCLIENTENCODING work again and uses bsearch() instead of
> iterating over the array of guc variables in guc_get_index().
Applied.
--
Peter E
hackers. My original suggestion was
> "pgforensics". "pgdiagfuncs" and "pginspect" were also suggested, among
> others. I'm still open to suggestions, though. Have any?
Something involving "page" would at least explain what you can diagnose.
the default and now they would
be testing a different default.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 7: You can help support the PostgreSQL project by donating at
http://www.po
Heikki Linnakangas wrote:
> Here's an update of Simon's Heap Page Diagnostic Functions. I now
> consider it ready to commit.
How is this better than pg_filedump?
"diagnostics" is an awfully general name, too.
--
Peter Eisentraut
http://develo
the memory pool and copies an
> existing string into it.
How is that different from pstrdup()?
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
This would be easy to do and might be useful even for 8.3. But I don't
really know how to label that. Having a contrib/xslt alongside
contrib/xml2 would probably be confusing. Ideas?
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broad
ou select a feature, then it's built, or you
don't, then it's not. So the only options we really have are adding
another switch for libxslt, or including it with libxml. I'm not sure
which is better.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
-
if any).
>
> Is that legal XML? I though only documents could have prologs.
It's not a legal XML document, but it's a legal XML content fragment,
specified by SQL/XML.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 6: explain analyze is your friend
anks. 8.1 and 8.2 have the same typo -- any reason not to
> > backpatch this?
>
> OK, fixed in 8.2.X. We don't patch documentation past the most
> recent major release.
Why not?
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of b
and applied. I don't see any other cases of
> this in our documentation.
That doesn't mean this one isn't useful. Please revert this.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
T
mand of this form from
some other implementation and don't know what it means.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
contrib Makefile (use the
> individual module Makefiles instead), or
> . change the xml2 Makefile
Any of these could be worth considering, but it needs to be thought
through first.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)--
Andrew Dunstan wrote:
> Since contrib/xml2 seems to be staying with us at least for now, this
> small patch enables it to be built and installed from the contrib
> Makefile when --with-libxml is given to configure.
contrib/xml2 also requires libxslt.
--
Peter Eisent
(data), (xmlChar *) "bar' IS DOCUMENT;
?column?
--
t
(1 row)
pei=# select xml 'barbar' IS
DOCUMENT;
?column?
--
f
(1 row)
pei=# select xml 'bar' IS DOCUMENT;
?column?
--
t
(1 row)
pei=# select xml 'barbar' IS DOCUMENT;
?column
pper element themselves?
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
result
of the XPath expression cannot be evaluated with certainty. If no namespace
mapping is to be passed, then you should pass a list(/array/...) of length
zero.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
n is probably not the best possible one, but
what the xpath() code does it totally wrong nevertheless.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http
1 - 100 of 821 matches
Mail list logo
