Re: Concurrent connections in psql - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Concurrent connections in psql
Date
Msg-id 1175025398.4386.181.camel@silverbirch.site
Whole thread Raw
In response to Re: Concurrent connections in psql  (Heikki Linnakangas <heikki@enterprisedb.com>)
Responses Re: Concurrent connections in psql  (Andrew Dunstan <andrew@dunslane.net>)
Re: Concurrent connections in psql  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Tue, 2007-03-27 at 18:16 +0100, Heikki Linnakangas wrote:
> Bruce Momjian wrote:
> > Yes, yes.  I would like to have used it when testing the MyProc->xmin
> > improvements.  The only thing that has held it back from being applied
> > was that there was no documentation/examples of how it would be used.
> 
> Hear hear! I had trouble writing regression tests for the MVCC-safe 
> cluster patch. Had I had an up-to-date version at hand, I would've used it.
> 
> I haven't looked at the psql source code, but would it be possible to 
> clean it up to make it less tangled and ugly, while you're at it?

Greg,

It sounds like we still need to remove the \cwait command, yes??
If we are going to perform that surgery, it probably should be you,
sorry. Others may have input on the internal implementation but its your
name on the tin.

I would love, love, love to be able to use this syntax within pg_dump as
well, so we can create multiple indexes in parallel at restore time.
Anyone fancy adding that as well? We should be able to speed up overall
index builds by x2 using concurrent builds.

--  Simon Riggs              EnterpriseDB   http://www.enterprisedb.com




pgsql-hackers by date:

Previous
From: "Joris Dobbelsteen"
Date:
Subject: Re: Guarenteeing complex referencial integrity throughcustom triggers
Next
From: "Simon Riggs"
Date:
Subject: Re: [GENERAL] Priorities for users or queries?