Following patch is a minor addition to postgres.c that allows the two
existing statement logging techniques to work with V3 exec. This then
allows statement logging with PostgreSQL 8.0+ for JDBC and other V3
connection types.
The rationale of this patch is to add functionality without modifying
I have access to a system with locale of UTF-8. cvstip would no longer
initdb on this system, as a result of recent renaming of UTF-8 to UTF8.
i.e.
[EMAIL PROTECTED] ~]$ locale
LANG=en_US.UTF-8
LC_CTYPE=en_US.UTF-8
LC_NUMERIC=en_US.UTF-8
LC_TIME=en_US.UTF-8
LC_COLLATE=en_US.UTF-8
This would explain the similar failure that I reported and didn't get
around to digging into. Excellent.
andrew
Simon Riggs wrote:
I have access to a system with locale of UTF-8. cvstip would no longer
initdb on this system, as a result of recent renaming of UTF-8 to UTF8.
i.e.
[EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Quick patch to adress a recent concern on the mailing list
about adding an errant TO when we already have a TO. Since
TO cannot be a valid column name (we must quote it), we can
simply ignore the tab-completion if the previous word
was a TO
- --
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
In response to Bruce's recent question, and remembering the recent
scolding received about removing a LEFT from an unrelated patch :),
here's a patch that does that and nothing more: removes all
unnecessary left joins from psql. Done in the theory
Greg Sabino Mullane [EMAIL PROTECTED] writes:
else if (pg_strcasecmp(prev4_wd, TABLE) == 0
!pg_strcasecmp(prev2_wd, RENAME) == 0
!pg_strcasecmp(prev_wd, TO))
COMPLETE_WITH_CONST(TO);
In order to be
