On Wed, Apr 12, 2006 at 05:25:47PM +0100, Dave Page wrote:
> The driver implements all versions of the wire protocol itself, but if
> libpq is available at runtime (it will dynamically load it on platforms
> that support it) it can use it for connection setup so features like SSL
> can be provided
On Wed, Apr 12, 2006 at 05:00:17PM -0400, Tom Lane wrote:
> > Issuer (name and certificate), validity dates, basic constraints, key
> > usage, posslby fingerprint.
>
> I think that way madness lies --- do we really want to commit to
> re-inventing an SSL API that will cover anything someone might w
Bruce Momjian writes:
> Bruno Almeida do Lago wrote:
>> After that night, I started to ask myself if PostgreSQL should not have a
>> control file to check if expected datafiles are where they should be and
>> JUST warn about missing ones?
> I don't think this happens frequently enough to add code
Tom Lane wrote:
> "Magnus Hagander" <[EMAIL PROTECTED]> writes:
> > While we're talking about pgstats... There was some talk a while back
> > about the whole bufferer/collector combination perhaps being unnecessary
> > as well, and that it might be a good idea to simplify it down to just a
> > col
Bruno Almeida do Lago wrote:
> DBA takes another coffee and finally started the database which... just came
> up! Few minutes latter lot off errors being displayed. What is that???
> /mnt/array2 (50% of datafiles and tablespaces were there) was still umounted
> and even so PostgreSQL came up. -- Po
On Wed, Apr 12, 2006 at 07:28:25PM -0400, Alvaro Herrera wrote:
> Dave Page escribi?:
>
> > > Alvaro Herrera <[EMAIL PROTECTED]> writes:
> > > > It would be nice to see the "visual explain" tool that Denis wrote --
> > > > did he finish it? Is it available somewhere? Are there any
> > > > scree
Dave Page escribió:
> > Alvaro Herrera <[EMAIL PROTECTED]> writes:
> > > It would be nice to see the "visual explain" tool that Denis wrote --
> > > did he finish it? Is it available somewhere? Are there any screenshots?
>
> > Red Hat did one of these some years ago:
> > http://sources.redhat.c
On Wed, Apr 12, 2006 at 03:34:05PM -0700, Josh Berkus wrote:
> If we have an XML patch now, I say use it. I know I want it.
Certainly; XML is better than nothing. But since it shouldn't be hard to
add the ability to output a recordset at the same time...
--
Jim C. Nasby, Sr. Engineering Consult
Martijn van Oosterhout wrote:
>On Wed, Apr 12, 2006 at 05:03:32PM +0100, Dave Page wrote:
>
>
>
>
>>The next version of psqlODBC (that has just gone into CVS tip after
>>months of work and debate) uses it, and would break almost completely
>>should it be removed, therefore any backwards incompat
"Jim C. Nasby" <[EMAIL PROTECTED]> writes:
> Having an SQL format would make it easier to allow for a mode that
> captures explain or explain analyze output from every query. Turn that
> mode on, run an application's test suite, and now you have a pretty good
> idea of how all the queries will ru
Jim,
> The list goes on. Like I said, you could do all these things with XML,
> you just couldn't easily do them within the database.
XML --> Table conversion should be relatively easy with PL/Perl, PL/Java,
and/or an external language. Heck, if we could expand our XML tools
(Peter will have
-Original Message-
From: "Tom Lane"<[EMAIL PROTECTED]>
Sent: 12/04/06 23:03:08
To: "Alvaro Herrera"<[EMAIL PROTECTED]>
Cc: "Germán Poó Caamaño"<[EMAIL PROTECTED]>, "Jim C. Nasby"<[EMAIL PROTECTED]>,
"[EMAIL PROTECTED]"<[EMAIL PROTECTED]>,
"pgsql-hackers@postgresql.org"
Subject: Re: [HAC
Ühel kenal päeval, K, 2006-04-12 kell 17:42, kirjutas Alvaro Herrera:
> It would be nice to see the "visual explain" tool that Denis wrote --
> did he finish it? Is it available somewhere? Are there any screenshots?
IIRC there is a "visual explain" tool pin pgAdmin III
---
Hannu
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> It would be nice to see the "visual explain" tool that Denis wrote --
> did he finish it? Is it available somewhere? Are there any screenshots?
Red Hat did one of these some years ago:
http://sources.redhat.com/rhdb/visualexplain.html
I don't see a pr
Ühel kenal päeval, K, 2006-04-12 kell 14:38, kirjutas Jim C. Nasby:
> Well, really just about anything you'd want to do with it in an XML
> format. The advantage of SQL is that you can do it within the database,
> and you don't have to worry about having something around that can
> process XML.
>
Hi,
Germán Poó Caamaño escribió:
> We can get the best of both worlds.
>
> For instance, EXPLAIN and EXPLAIN ANALYZE with the usual output; but
> also EXPLAIN XML and EXPLAIN ANALYZE XML with an XML syntax to be
> used by programs.
>
> I have a patch for this behavior, but unfortunately this i
"Magnus Hagander" <[EMAIL PROTECTED]> writes:
>> Other than DN and CN, what else would people want?
> Issuer (name and certificate), validity dates, basic constraints, key
> usage, posslby fingerprint.
I think that way madness lies --- do we really want to commit to
re-inventing an SSL API that w
On Wed, 2006-04-12 at 14:38 -0500, Jim C. Nasby wrote:
> On Wed, Apr 12, 2006 at 09:45:41AM -0700, Mischa Sandberg wrote:
> > Jim C. Nasby wrote:
> > >On Wed, Apr 12, 2006 at 04:53:20PM +0200, Thomas Hallgren wrote:
> > >
> > >>
> > >>
> > >>
> > >>
> > >>
> > >
> > >
> > >Well, the downs
[short]
This probably would be an uneasy fit into generic backend code.
Was hoping the GPUSort project might have fleeced/sorted out some issues.
[long]
Simon Riggs wrote:
On Wed, 2006-04-12 at 10:00 -0700, Mischa Sandberg wrote:
...
Long answer: we're shipping a server (appliance) product buil
On Wed, Apr 12, 2006 at 09:45:41AM -0700, Mischa Sandberg wrote:
> Jim C. Nasby wrote:
> >On Wed, Apr 12, 2006 at 04:53:20PM +0200, Thomas Hallgren wrote:
> >
> >>
> >>
> >>
> >>
> >>
> >
> >
> >Well, the downside is that such a format means explain output is now
> >twice as long. But I'd
On Wed, 2006-04-12 at 10:00 -0700, Mischa Sandberg wrote:
> Martijn van Oosterhout wrote:
> > On Tue, Apr 11, 2006 at 04:02:07PM -0700, Mischa Sandberg wrote:
> >
> >>Anybody on this list hear/opine anything pf the GPUSort project for
> >>postgresql? I'm working on a radix-sort subcase for tuples
On Wed, Apr 12, 2006 at 08:14:58PM +0200, Magnus Hagander wrote:
> > Other than DN and CN, what else would people want?
>
> Issuer (name and certificate), validity dates, basic constraints, key
> usage, posslby fingerprint.
GnuTLS handles this with just one function:
gnutls_x509_crt_get_dn_by_oi
> > There is a more serious issue here though: if we allow more
> than one
> > SSL library, what exactly can an application safely do with the
> > returned pointer? It strikes me as very dangerous for the app to
> > assume it knows which SSL library is underneath libpq. It's not at
> > all h
On Wed, Apr 12, 2006 at 12:32:01PM -0400, Tom Lane wrote:
> There is a more serious issue here though: if we allow more than one SSL
> library, what exactly can an application safely do with the returned
> pointer? It strikes me as very dangerous for the app to assume it knows
> which SSL library
On Wed, Apr 12, 2006 at 01:42:51PM -0400, Stephen Frost wrote:
> * Andreas Pflug ([EMAIL PROTECTED]) wrote:
> > I wonder if there are apps that actually use the ssl pointer, beyond
> > detection of encrypted connections. So interpreting the result as bool
> > would be sufficient.
>
> I'm not sur
* Andreas Pflug ([EMAIL PROTECTED]) wrote:
> I wonder if there are apps that actually use the ssl pointer, beyond
> detection of encrypted connections. So interpreting the result as bool
> would be sufficient.
I'm not sure if there are apps out there which use it for anything but a
bool but ther
* Tom Lane ([EMAIL PROTECTED]) wrote:
> Martijn van Oosterhout writes:
> > 1. Changing it to always return (void*), irrespective of SSL
> > ...
> > Personally, I'm in favour of 1, because then we can get rid of the
> > #include for openssl, so users don't have to have openssl headers
> > installed
Eric Lauzon wrote:
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Merlin Moncure
Sent: 12 avril 2006 12:22
To: Neil Conway
Cc: Tom Lane; David Fetter; Jim C. Nasby; Joshua D. Drake;
[EMAIL PROTECTED]; pgsql-hackers@postgresql.org
Subject: Re: [HACKE
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Merlin Moncure
> Sent: 12 avril 2006 12:22
> To: Neil Conway
> Cc: Tom Lane; David Fetter; Jim C. Nasby; Joshua D. Drake;
> [EMAIL PROTECTED]; pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] p
Tom Lane wrote:
Martijn van Oosterhout writes:
1. Changing it to always return (void*), irrespective of SSL
...
Personally, I'm in favour of 1, because then we can get rid of the
#include for openssl, so users don't have to have openssl headers
installed to compile postgresql programs.
I li
Greg Sabino Mullane wrote:
I wonder if it would help much just to change EXPLAIN to indent with
something other than spaces?
I like that. Maybe even decrease the indenting a little more, and compress
some of the inner whitespace (such as the 2 spaces after the operator name)
Might it be wort
Martijn van Oosterhout wrote:
On Tue, Apr 11, 2006 at 04:02:07PM -0700, Mischa Sandberg wrote:
Anybody on this list hear/opine anything pf the GPUSort project for
postgresql? I'm working on a radix-sort subcase for tuplesort, and there
are similarities.
http://www.andrew.cmu.edu/user/ngm/15-
Jim C. Nasby wrote:
On Wed, Apr 12, 2006 at 04:53:20PM +0200, Thomas Hallgren wrote:
Well, the downside is that such a format means explain output is now
twice as long. But I'd love to see something like that as an option. I'd
also still like to see an SQL-parseable version as
Martijn van Oosterhout writes:
> 1. Changing it to always return (void*), irrespective of SSL
> ...
> Personally, I'm in favour of 1, because then we can get rid of the
> #include for openssl, so users don't have to have openssl headers
> installed to compile postgresql programs.
I like that too.
> -Original Message-
> From: Martijn van Oosterhout [mailto:[EMAIL PROTECTED]
> Sent: 12 April 2006 17:15
> To: Dave Page
> Cc: pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] Practical impediment to supporting
> multiple SSL libraries
>
> On Wed, Apr 12, 2006 at 05:03:32PM +010
On 4/11/06, Neil Conway <[EMAIL PROTECTED]> wrote:
> On Tue, 2006-04-11 at 17:20 -0400, Tom Lane wrote:
> > No, I'm saying that having access to a PL renders certain classes of
> > attacks significantly more efficient. A determined attacker with
> > unlimited time may not care, but in the real wor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> I wonder if it would help much just to change EXPLAIN to indent with
> something other than spaces?
I like that. Maybe even decrease the indenting a little more, and compress
some of the inner whitespace (such as the 2 spaces after the operator na
On Wed, Apr 12, 2006 at 05:03:32PM +0100, Dave Page wrote:
> The next version of psqlODBC (that has just gone into CVS tip after
> months of work and debate) uses it, and would break almost completely
> should it be removed, therefore any backwards incompatible change should
> be avoided imho. An
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Martijn van Oosterhout
> Sent: 12 April 2006 16:48
> To: pgsql-hackers@postgresql.org
> Subject: [HACKERS] Practical impediment to supporting
> multiple SSL libraries
>
> Just quickly going thro
On Wed, Apr 12, 2006 at 12:32:52PM +0200, Peter Eisentraut wrote:
> Am Dienstag, 11. April 2006 23:20 schrieb Tom Lane:
> > In the end it's only one small component of security, but any
> > security expert will tell you that you take all the layers of
> > security that you can get.
>
> I think wha
Just quickly going through what might be needed to support multiple SSL
libraries revealed one big problem in libpq-fe.h.
#ifdef USE_SSL
/* Get the SSL structure associated with a connection */
extern SSL *PQgetssl(PGconn *conn);
#else
extern void *PQgetssl(PGconn *conn);
#endif
The return type o
Ühel kenal päeval, K, 2006-04-12 kell 10:29, kirjutas Jim C. Nasby:
> On Wed, Apr 12, 2006 at 04:53:20PM +0200, Thomas Hallgren wrote:
> >
> >
> >
> >
> >
>
> Well, the downside is that such a format means explain output is now
> twice as long.
You can place end tags differently
On Wed, Apr 12, 2006 at 04:53:20PM +0200, Thomas Hallgren wrote:
>
>
>
>
>
Well, the downside is that such a format means explain output is now
twice as long. But I'd love to see something like that as an option. I'd
also still like to see an SQL-parseable version as well, since I
Richard Huxton wrote:
Tom Lane wrote:
I dislike the thought of encouraging people to post stuff in a
not-easily-readable format. They won't do it anyway, if it's not
default; look how we still can't get people to send EXPLAIN ANALYZE
output the first time.
It certainly needs to be one format
>
> I wonder if Oracle ever recommended disabling PL/SQL (not to
> mention MS Transact-SQL)...
>
Don't know abiout Oracle, but you can't disable Transact-SQL in SQL
Server 7.0 or 2000 (don't know about 2003^h5) because Enterprise Manager
and sp_help* require it.
And +1 for not installing plpgs
Dave Page wrote:
Keeping PostgreSQL as secure as possible out of the box pretty much
requires us to do the same in my mind - if an major feature such as
pl/pgsql is easy for the user to enable should they want it, then it
should be disabled by default to minimise the number of attack vectors
Tom Lane wrote:
I dislike the thought of encouraging people to post stuff in a
not-easily-readable format. They won't do it anyway, if it's not
default; look how we still can't get people to send EXPLAIN ANALYZE
output the first time.
It certainly needs to be one format for both purposes.
O
Richard Huxton writes:
> Jim C. Nasby wrote:
>> Actually, I've been wondering about better ways to handle this. One
>> thought is to come up with a non-human readable format that could easily
>> be cut and pasted into a website that would then provide something easy
>> to understand. Ideally that
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Peter Eisentraut
> Sent: 12 April 2006 11:33
> To: pgsql-hackers@postgresql.org
> Cc: Tom Lane; David Fetter; Jim C. Nasby; Joshua D. Drake;
> [EMAIL PROTECTED]
> Subject: Re: [HACKERS] plpgsql b
Am Dienstag, 11. April 2006 23:20 schrieb Tom Lane:
> In the end it's only one small component of security, but any security
> expert will tell you that you take all the layers of security that you
> can get.
I think what the security experts are saying is that you need a thorough
evaluation of a
Hi Gaetano,
On Tue, 2006-04-11 at 18:31 +0200, Gaetano Mendola wrote:
> I'm trying to build the rpms for RH9,
> I downloaded the srpm for RH9 but I'm stuck on these errors:
>
> Attempt a:
>
> # rpmbuild --rebuild postgresql-8.0.7-1PGDG.src.rpm
> Installing postgresql-8.0.7-1PGDG.src.rpm
> error:
> >> The attached patch allows SET CONSTRAINTS to take a schema
qualified
> >> constraint name (myschema.t1_fk_t2) and when given a bare
constraint name
> >> it uses the search_path to determine the matching constraint
instead of
> >> the previous behavior of disabling all identically named
constr
Jim C. Nasby wrote:
On Mon, Apr 10, 2006 at 10:44:15AM +0100, Richard Huxton wrote:
Bruce Momjian wrote:
* Allow EXPLAIN output to be more easily processed by scripts
Can I request an extension/additional point?
* Design EXPLAIN output to survive cut & paste on mailing-lists
Being ab
53 matches
Mail list logo
