-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, Jan 06, 2008 at 01:12:32AM +0530, Gokulakannan Somasundaram wrote:
> On Jan 5, 2008 6:15 PM, <[EMAIL PROTECTED]> wrote:
>
> >
> > One thought I had back then, with partitioned tables was "gee -- B-tree
> > index is already doing a partition; w
I wrote:
> It's possible that we could teach 8.3 to propagate the constant and keep
> the join condition in cases like this;
I think we actually can do this without too big a change. The main
problem is that initsplan.c doesn't put the upper outer join's clause
into the list of mergejoinable oute
On Saturday 05 January 2008 14:02, Markus Schiltknecht wrote:
> >> To satisfy all the different requirements of partitioning with segments
> >> based partitioning, we'd have to allow a table to span multiple table
> >> spaces. I'm not very keen on going that way.
> >
> > Why?
>
> Uh.. if a table (R
Mark Mielke wrote:
> Does the patch handle patched clients connecting to unpatched servers
> and vice versa?
Yes, it is all compatible.
> Cryptographic
> authentication and encrypted data stream cost is high compared to no
> cryptographic authentication or encrypted data streams. I don't know if
On Jan 5, 2008 6:15 PM, <[EMAIL PROTECTED]> wrote:
>
> One thought I had back then, with partitioned tables was "gee -- B-tree
> index is already doing a partition; why do a manual partition on top of
> that?".
>
> Can you please explain more on what you are trying to say here?
Thanks,
Gokul.
Tom Lane wrote:
Peter Eisentraut <[EMAIL PROTECTED]> writes:
Here is a patch that implements "localssl" as well. It is quite simple.
The other area that would need some thought before we could consider
this "done" is the behavior of libpq's sslmode parameter. With the
patch as given,
Hi,
Robert Treat wrote:
Personally I cant say it complicates things, because it isn't clear how it
will be managed. :-)
Well, management of relations is easy enough, known to the DBA and most
importantly: it already exists. Having to set up something which is
*not* tied to a relation complic
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Here is a patch that implements "localssl" as well. It is quite simple.
The other area that would need some thought before we could consider
this "done" is the behavior of libpq's sslmode parameter. With the
patch as given, an SSL-capable libpq wi
On Saturday 05 January 2008 10:42, Markus Schiltknecht wrote:
> > The main proposal deliberately has few, if any, knobs and dials. That's
> > a point of philosophy that I've had views on previously: my normal
> > stance is that we need some knobs to allow the database to be tuned to
> > individual
Hi,
Simon Riggs wrote:
> On Fri, 2008-01-04 at 22:26 +0100, Markus Schiltknecht wrote:
>
>> I'm still puzzled about how a DBA is expected to figure out which
>> segments to mark. Simon, are you assuming we are going to pass on
>> segment numbers to the DBA one day?
>
> No Way!
Ah, I'm glad ;-)
Hi,
[EMAIL PROTECTED] wrote:
The main proposal deliberately has few, if any, knobs and dials. That's
a point of philosophy that I've had views on previously: my normal
stance is that we need some knobs to allow the database to be tuned to
individual circumstances.
One thought I had back then,
May be this is not the right place to post this, if not please move the post.
Would it be possible to add an option to the pg 8.3 Windows installer to
separate the pg_log and pg_xlog folders from tha data one?
I plan to install 8.3 on a dedicated server and i want to separate the data
from the W
Bruce Momjian wrote:
> Peter Eisentraut wrote:
> > Using the attached patch, SSL will act over Unix-domain sockets. AFAICT,
> > this just works. I didn't find a way to sniff a Unix-domain socket,
> > however.
> >
> > How should we proceed with this?
>
> I am confused by the shortness of this patc
Jari Aalto wrote:
> Here is usggestion to add URL to documentation.
But there are other sources for the documentation. It might be preferrable to
use a local copy. Furthermore I think it is fairly obvious that you can find
documentation on the website.
--
Peter Eisentraut
http://developer.po
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, Jan 05, 2008 at 09:33:45AM +, Simon Riggs wrote:
[...]
> The main proposal deliberately has few, if any, knobs and dials. That's
> a point of philosophy that I've had views on previously: my normal
> stance is that we need some knobs to a
I'm away now until Wed 9 Jan, off-line except by phone for emergencies.
I expect to catch up immediately upon my return.
--
Simon Riggs
2ndQuadrant http://www.2ndQuadrant.com
---(end of broadcast)---
TIP 7: You can help support the PostgreS
On Fri, 2008-01-04 at 17:28 +0900, Fujii Masao wrote:
> Simon Riggs wrote:
>
> > My original one line change described on bug 3843 seems like the best
> > solution for 8.3.
> >
>
> +1
> Is this change in time for RC1?
Patch attached.
--
Simon Riggs
2ndQuadrant http://www.2ndQuadrant.com
Here is usggestion to add URL to documentation.
This patch is against git://repo.or.cz/PostgreSQL.git
Jari
>From 054ce704ba1368bb3f895c5ac3f7d05ee1782795 Mon Sep 17 00:00:00 2001
From: Jari Aalto
Date: Fri, 4 Jan 2008 10:00:12 +0200
Subject: [PATCH] pg_hba.conf.sample: mention www.postgresql.or
Andrew Sullivan wrote:
On Fri, Jan 04, 2008 at 10:26:54PM +0100, Markus Schiltknecht wrote:
I'm still puzzled about how a DBA is expected to figure out which
segments to mark.
I think that part might be hand-wavy still. But once this facility is
there, what's to prevent the current active se
On Fri, 2008-01-04 at 22:31 -0500, Robert Treat wrote:
> Not to be negative, but istm how this feature would be managed is as
> important
> as the bits under the hood.
Agreed. On this part of the thread, we've been discussing an extension
to the basic proposal, which is why I have not been con
20 matches
Mail list logo
