On Mon, Nov 12, 2012 at 8:45 PM, Mike Toews <mwtoews@gmail.com> wrote:
> I'm not sure if this is worth documenting, but pg_dumping mixed-case tables
> with the '-t table' option appears to not be accurately documented for
> cmd.exe. Here are my four attempts, with only the last as success:
I believe this complaint is basically the same as this recent one:
http://archives.postgresql.org/pgsql-bugs/2012-10/msg00044.php
and this behavior confused me recently as well. I agree the behavior
should be documented, though it should be documented for all our
utilities which accept a --table argument and pass it on as a
supposedly already-escaped identifier.
Incidentally, I'm really not fond of the existing behavior because it:
a.) is counterintuitive
b.) requires the user to escape table names themselves, and how were
they even supposed to have a chance of programmatically doing this
properly before we exposed PQescapeIdentifier()
c.) opens possible SQL injection holes, e.g.
reindexdb --table='foo; ALTER ROLE limited WITH superuser'
Josh
