On Thu, 2008-05-01 at 12:30 -0400, Tom Lane wrote:
It's May 1st, which means it's time for our second 8.4 commit fest.
I took a quick look through my inbox and added some pending patches to
http://wiki.postgresql.org/wiki/CommitFest:May
but it's entirely likely there are still some missing
On Friday 02 May 2008 13:35:27 Simon Riggs wrote:
On Fri, 2008-05-02 at 12:01 -0400, Tom Lane wrote:
Heikki Linnakangas [EMAIL PROTECTED] writes:
Simon Riggs wrote:
* We've said here http://www.postgresql.org/docs/faqs.TODO.html that
we Don't want hints. If that's what we really think,
Brendan Jurd [EMAIL PROTECTED] writes:
Well ... if somebody does want to change the representation of xml
down the road, he's going to have to touch all the sites where the
code converts to and from cstring anyway, right?
True.
With that in mind, please find attached my followup patch. It
stephen layland [EMAIL PROTECTED] writes:
I've written a quick patch against the head branch (8.4DEV, but it also
works with 8.1.3 sources) to fix LDAP authentication support to
work with LDAPS servers that do not need start TLS. I'd be interested
to hear your opinions on this.
Not being an
* Thomas Mueller:
What do you think about it? Do you think it makes sense to implement
this security feature in PostgreSQL as well?
Can't this be implemented in the client library, or a wrapper around it?
A simple approximation would be to raise an error when you encounter a
query string that
Euler Taveira de Oliveira wrote:
Andrew Dunstan wrote:
Committed with slight editorializing. Statement timeout was only
introduced in 7.3, whereas pg_dump can dump from much older versions
of Postgres.
You forget a ; in this committ [1].
[1]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi -hackers,
In another thread about GUC parameter cursors_tuple_fraction, the
debate seems to drift onto query hints. About which the consensus here
is pretty clear and strong, no query hints in PostgreSQL, thanks, or
we're never gonna have a
