From: | "Greg Sabino Mullane" <greg(at)turnstep(dot)com> |
---|---|
To: | pgsql-patches(at)postgresql(dot)org |
Subject: | Re: Remove unneeded left joins from psql |
Date: | 2005-04-13 01:22:33 |
Message-ID: | c827c8f448048e77edd6f7a0bc299577@biglumber.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> I'm still not happy about this. "Joining column is not null" has
> nothing to do with it --- what is at issue is whether there is certain
> to be a match. Since we do not have foreign-key enforcement on the
> system catalog interrelationships, it is possible for system bugs or
> manual intervention to create non-matching situations.
Yes, you are right about this: we should fail in a way that puts a null
schema rather than not matching at all. Must get more sleep before
blindly patching next time. :)
- --
Greg Sabino Mullane greg(at)turnstep(dot)com
PGP Key: 0x14964AC8 200504122121
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----
iD8DBQFCXHRhvJuQZxSWSsgRAv8yAJ97xvvNVJ5Tvcwlr7f5mIDqtXBqpACgkvro
pvWsWqanqcTnfO9thU8n0j4=
=aYbU
-----END PGP SIGNATURE-----
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Kirkwood | 2005-04-14 04:11:13 | Re: Proof of concept for MIN/MAX optimization |
Previous Message | Simon Riggs | 2005-04-12 17:38:39 | Re: COPY Fillfactor patch |