On Mon, 3 Apr 2006 06:13 am, Neil Conway wrote:
> I've committed a patch to HEAD that should improve this behavior. Let me
> know if the current behavior is still unsatisfactory.
Yes, thanks, it fixes the stuff that bugged me:
[EMAIL PROTECTED] pgsql]$ psql -p5434 -dpyarra
[snip opening car chase
On Thu, 2006-03-30 at 11:20 +1000, Philip Yarra wrote:
> Hi folks, I've found that CVS HEAD psql's \c doesn't quite behave as expected
> when postmaster is listening on non-default port.
I've committed a patch to HEAD that should improve this behavior. Let me
know if the current behavior is still
On Wed, Mar 29, 2006 at 10:19:51PM -0500, Tom Lane wrote:
> Philip Yarra <[EMAIL PROTECTED]> writes:
> > Hi folks, I've found that CVS HEAD psql's \c doesn't quite behave as
> > expected
>
> Yeah, there were complaints about this already. I think the problem was
> introduced by this patch:
I se
Philip Yarra <[EMAIL PROTECTED]> writes:
> Hi folks, I've found that CVS HEAD psql's \c doesn't quite behave as
> expected
Yeah, there were complaints about this already. I think the problem was
introduced by this patch:
2006-02-11 21:54 momjian
* doc/src/sgml/ref/psql-ref.sgml, src/b
Hi folks, I've found that CVS HEAD psql's \c doesn't quite behave as expected
when postmaster is listening on non-default port. In this case I have
postmaster listening on port 5434:
[EMAIL PROTECTED] pgsql]$ /usr/local/pgsql-cvs-head/bin/psql -p5434 -dpyarra
Welcome to psql 8.2devel, the Postgr
