From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | Jan Wieck <wieck(at)debis(dot)com>, pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] Parallel regress tests (was Re: FOREIGN KEY and |
Date: | 1999-12-07 23:04:51 |
Message-ID: | 24940.944607891@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Peter Eisentraut <e99re41(at)DoCS(dot)UU(dot)SE> writes:
>> Peter, could you please add some switch to psql that
>> activates an fflush() whenever psql would like to read more
>> input commands. In the meantime I can start to write the
>> driver using the v6.5 psql.
> I'm going to go an a flush hunt...
Offhand I see no reason why psql shouldn't *always* fflush its output
before reading a new command. It'd waste a few microseconds per command
when reading from a file, but that'd hardly be noticeable in the great
scheme of things. Adding another switch is just offering another way
for people to make a mistake...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff MacDonald <jeff@pgsql.com> | 1999-12-07 23:15:40 | Re: [GENERAL] Oft Ask: How to contribute to PostgreSQL? |
Previous Message | Keith Parks | 1999-12-07 22:38:08 | Table aliases in delete statements? |