postgres: add the ability to specify a list of tables to be treated as layers

[cph]

This functionality is already available for other datasources(as per FrankW). This feature is really needed as it is a huge performance problem when we only want to export 1 table from a system with 100's of tables listed in the geometry_columns table.

[warmerdam]

Mateusz,

I'd like you to add a way of specifying a table list is the PG: connection string. Perhaps an entry like TABLES=name1,name2,... could be allow to establish the set of tables to be scanned. This would need to be removed from the string before the rest is passed on to the postgres connection opening function.

[project10]

patch implementing #1699

[project10]

This patch allows the list of tables to be specified in the manner Frank suggests. Doing so skips enumeration of the spatial tables from the database metadata.

Includes documentation update and minor documentation style and grammar issue fixes.

[Even Rouault]

Patch commited in trunk in r14204 (with minor adaptations related to memory usage).

Is this appropriate for backporting into 1.5 branch ?

[Even Rouault]

Answering to myself ;-), I don't think it's appropriate. There have been quite a lot of changes in the postgres driver since 1.5 and that one is really new feature.

Closing