v.in.ogr with postgis layers fails if the table schema is on the first place in the search_path of the database

[tomdb]

The command

v.in.ogr  dsn="PG:dbname=XXX user=XXX host=XXX" layer=venue.stand_lines output=lines type=boundary

fails if the schema "venue" is on the first place of the search path of the database XXX. The same command without the schema definition ( "layer=stand_lines") works fine as expected. Examples:

XXX=>ALTER DATABASE XXX set search_path = venue,public;

GRASS 6.4.1 (xy):~/grassdata/xy >v.in.ogr dsn="PG:dbname=XXX user=XXX host=localhost " layer=venue.stand_lines output=lines type=boundary --overwrite
WARNING: Vector map <lines> already exists and will be overwritten
ERROR: Layer <venue.stand_lines> not available

XXX=>ALTER DATABASE XXX set search_path = venue,public;

GRASS 6.4.1 (xy):~/grassdata/xy >v.in.ogr dsn="PG:dbname=XXX user=XXX host=localhost " layer=stand_lines output=lines type=boundary --overwrite

...works fine....

XXX=>ALTER DATABASE XXX set search_path = public,venue;

GRASS 6.4.1 (xy):~/grassdata/xy > v.in.ogr dsn="PG:dbname=XXX user=XXX host=localhost " layer=venue.stand_lines output=lines type=boundary --overwrite

...works fine....

XXX=>ALTER DATABASE XXX set search_path = venue,public;

GRASS 6.4.1 (xy):~/grassdata/xy > v.in.ogr  dsn="PG:dbname=XXX user=XXX host=localhost " layer=stand_lines output=lines type=boundary --overwrite

...works fine....

XXX=>ALTER DATABASE XXX set search_path = public;

GRASS 6.4.1 (xy):~/grassdata/xy > v.in.ogr  dsn="PG:dbname=XXX user=XXX host=localhost " layer=venue.stand_lines output=lines type=boundary --overwrite

...works fine....

[tomdb]

Postgres version:

XXX=> select version();
                                                      version                                                       
--------------------------------------------------------------------------------------------------------------------
 PostgreSQL 8.4.9 on x86_64-pc-linux-gnu, compiled by GCC gcc-4.5.real (Ubuntu/Linaro 4.5.2-8ubuntu4) 4.5.2, 64-bit

[tomdb]

Problem still present on Grass 7.0, PostgreSQL 9.3

[martinl]

Works in G76