RE: bug in psql?

["Aleksey M Boltenkov" <holybolt@xxxxxxxxxx>]

15.08.2020, 09:49, Pavel Stehule <pavel.stehule@xxxxxxxxx>

so 15. 8. 2020 v 8:35 odesílatel Aleksey M Boltenkov <holybolt@xxxxxxxxxx> napsal:

eksey M Boltenkov.

15.08.2020, 08:39, Pavel Stehule <pavel.stehule@xxxxxxxxx>

so 15. 8. 2020 v 7:35 odesílatel Aleksey M Boltenkov <holybolt@xxxxxxxxxx> napsal:

Is this a bug?

Executing of malformed (quote symbols) select in psql results in unexpected behaviour:

pg01:5432 postgres@db=# select 'any _expression_'any _expression_\d+;
List of relations
Schema │ Name │ Type │ Owner │ Size │ Description
════════╪══════════════════════════╪══════════╪══════════╪════════════╪══════════════
public │ geography_columns │ view │ postgres │ 0 bytes │
public │ geometry_columns │ view │ postgres │ 0 bytes │
public │ pg_buffercache │ view │ postgres │ 0 bytes │
public │ pg_stat_statements │ view │ postgres │ 0 bytes │
public │ raster_columns │ view │ postgres │ 0 bytes │
public │ raster_overviews │ view │ postgres │ 0 bytes │
public │ spatial_ref_sys │ table │ postgres │ 4616 kB │

...

I tested psql-12 and psql-14 and I don't see this issue

Pavel

Aleksey M Boltenkov.

You must have relations in search path, ifaiu.

engineer@pg02:~$ psql -U postgres -h localhost -p 5432 kaad
SET
Timing is on.
Null display is "¤".
Line style is unicode.
Unicode border line style is "single".
Unicode column line style is "single".
Unicode header line style is "double".
Output format is wrapped.
SET
Time: 0.234 ms
SET
Time: 0.206 ms
psql (12.4 (Ubuntu 12.4-1.pgdg18.04+1))
Type "help" for help.

2020-08-15 09:29:18 localhost:5432 postgres@kaad=# select version();
version
═════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════
PostgreSQL 12.4 (Ubuntu 12.4-1.pgdg18.04+1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0, 64-bit
(1 row)

Time: 6.682 ms
2020-08-15 09:29:24 localhost:5432 postgres@kaad=# select 'any _expression_'any _expression_\d+;
List of relations
Schema │ Name │ Type │ Owner │ Size │ Description
════════╪═══════════════════╪═══════╪══════════╪═════════╪═════════════
public │ geography_columns │ view │ postgres │ 0 bytes │
public │ geometry_columns │ view │ postgres │ 0 bytes │
public │ raster_columns │ view │ postgres │ 0 bytes │
public │ raster_overviews │ view │ postgres │ 0 bytes │
public │ spatial_ref_sys │ table │ postgres │ 4616 kB │
(5 rows)

[more] - > ; -- semicolon is manually added
ERROR: 42601: syntax error at or near "any"
LINE 1: select 'any _expression_'any _expression_
^
LOCATION: scanner_yyerror, scan.l:1149
Time: 0.530 ms

it is expected result from my perspective

there is same error if you run your query without \d

postgres=# select 'any _expression_ 'any _expression_;
ERROR:  syntax error at or near "any"
LINE 1: select 'any _expression_ 'any _expression_;
             

 

Aleksey M Boltenkov.

Thank you, i just was impressed by execution of part of malformed select _expression_ by psql as cli part.

Aleksey M Boltenkov.