Re: Concurrent psql API - Mailing list pgsql-hackers

From Gregory Stark
Subject Re: Concurrent psql API
Date
Msg-id 87ve2qulpp.fsf@oxford.xeocode.com
Whole thread Raw
In response to Re: Concurrent psql API  (Csaba Nagy <nagy@ecircle-ag.com>)
Responses Re: Concurrent psql API  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
"Csaba Nagy" <nagy@ecircle-ag.com> writes:

> For interactive use in the above mentioned scenario you can use the
> 'screen' command and start as many psqls as needed

Sure, or you could just start multiple xterms or emacs shell buffers 
(my preferred setup).

But I'm sure there are people who would prefer C-z too.

> So from my POV scripting should be the main case for such a feature...
> and there it would be welcome if it would be made easy to synchronize
> the different sessions.

I think it's the main case, that's why I didn't implement C-z at all. But I
think we should keep it as a design consideration and not preclude it in the
future.

Hm. I had a thought though. Perhaps C-z should just immediately start a new
connection. That would perhaps maintain the shell metaphor the way Tom was
thinking where you're always at a usable prompt. That might suck if you're at
a password-authenticated connection.

--  Gregory Stark EnterpriseDB          http://www.enterprisedb.com Ask me about EnterpriseDB's RemoteDBA services!


pgsql-hackers by date:

Previous
From: PFC
Date:
Subject: Re: Free Space Map data structure
Next
From: "Tom Dunstan"
Date:
Subject: Re: Commit fest queue