Stephen Frost <> writes:
> Sure, I was being a bit over-simplistic.  As was mentioned up-thread,
> the option would rather be "flip all-uppercase to lowercase and all-
> lowercase to uppercase, quote any which are mixed", or something along
> those lines.  What I was trying to get at is that it's up to the FDW
> what options it wants to support in this regard and we already have a
> way for the admin to pass in useful information to the FDW by way of the

> This, plus the generic ability to pass an OPTIONS clause to the IMPORT
> (allowing you to have different defaults for different IMPORT
> statements) and having it be transactional, as you mention, appears to
> be covering all the relevant bases.

Yeah, as far as the example of coping with differing case goes, I agree
that we'd want IMPORT to just follow whatever the FDW's default or
configured behavior is, since obviously the FDW will have to know how to
reverse the conversion when sending queries later on.  So there's no
apparent need for an IMPORT-level option *for that example*.  I'm not
sure if we need OPTIONS for IMPORT for any other uses.

                        regards, tom lane

Sent via pgsql-hackers mailing list (
To make changes to your subscription:

Reply via email to