Re: Testing with concurrent sessions

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: robertmhaas(at)gmail(dot)com, tgl(at)sss(dot)pgh(dot)pa(dot)us, andrew(at)dunslane(dot)net, peter_e(at)gmx(dot)net, david(at)kineticode(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Testing with concurrent sessions
Date: 2010-01-07 03:05:24
Message-ID: 20100107030524.GY6129@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Kevin Grittner escribió:

> Well, if that's the consensus, I have to choose between trying to
> implement multi-session psql and using testing which can't carry over
> to long-term regular use. Are we anywhere close to an agreement on
> what the multi-session psql implementation would look like? (If not
> I can put something forward.)

See
http://archives.postgresql.org/message-id/8204.1207689056@sss.pgh.pa.us
and followups.

--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2010-01-07 03:13:44 Re: [COMMITTERS] pgsql: Support ALTER TABLESPACE name SET/RESET ( tablespace_options ).
Previous Message Kevin Grittner 2010-01-07 03:00:30 Re: Testing with concurrent sessions