-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
> The use case is when you want to prepare a query, but only if it's not > already prepared on that connection. This has been covered before, but to reiterate: why would you need this? Any application worth its salt should be tracking which statements it has already prepared (after all, they cannot span connections). Seems a waste of resources to make a separate call to the database for information you should already know. - -- Greg Sabino Mullane [EMAIL PROTECTED] PGP Key: 0x14964AC8 200507151017 https://www.biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 -----BEGIN PGP SIGNATURE----- iEYEARECAAYFAkLXxcsACgkQvJuQZxSWSsgJOgCg+jKQzGW+Xgh+4rAooS01jxse fa0AnRG5ODx2N0gc8BG3LeYAYUVmICJX =eLkO -----END PGP SIGNATURE----- ---------------------------(end of broadcast)--------------------------- TIP 4: Have you searched our list archives? http://archives.postgresql.org