This testcase works in 7.3 but not in 7.4:
--
create table t1 (a int);
create table t2 (b int);
select * from t1, (select b as a from t2 group by a) as foo;
--
ERROR: column "t2.b" must appear in the GROUP BY cl
"Greg Sabino Mullane" <[EMAIL PROTECTED]> writes:
> I am trying to get version 7.4.2 installed on a Solaris box, but
> initdb fails because of shmmax being set too low. It does this
> even though initdb drops shared buffers as low as it can go (50).
> Is there any other way of getting around this l
"Magnus Hagander" <[EMAIL PROTECTED]> writes:
> In this case, SIGINT (query cancel) will not help, because all locks
> held by the transaction will still be held.
Wrong.
regards, tom lane
---(end of broadcast)---
TIP 6: Hav
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I am trying to get version 7.4.2 installed on a Solaris box, but
initdb fails because of shmmax being set too low. It does this
even though initdb drops shared buffers as low as it can go (50).
Is there any other way of getting around this limitati
Hi!
From what I can see, a "make check" runs the parallell tests and a "make
installcheck" runs the serial tests. Is there any special reason for
this? And for not providing a way to run the other kind of test
depending on the installation?
Stumbled across this when doing regress tests on win32,
>> Killing backends with runaway queries is a routine administrative
>> task.
>
>Cancelling runaway queries is a routine task. I'm less
>convinced that a
>remote kill (ie SIGTERM) facility is such a great idea.
Consider a scenario like:
User A starts transaction.
User A issues a LOCK TABLE (or d
