The following bug has been logged on the website:
Bug reference: 7899
Logged by: jov
Email address: am...@amutu.com
PostgreSQL version: 9.1.3
Operating system: CentOS 6
Description:
xxx=# select 2 from (select 1 as end) t;
?column?
--
2
(1 row)
x
"=?ISO-8859-1?B?Sm92?=" writes:
> xxx=# select end from (select 1 as end) t;
> ERROR: syntax error at or near "end"
> LINE 1: select end from (select 1 as end) t;
>^
You need to double-quote the outer use of "end", viz
regression=# select "end" from (select 1 as end) t;
end
--
I have get the description of this behaviour from doc 7.3.2
http://www.postgresql.org/docs/devel/static/queries-select-lists.html#QUERIES-COLUMN-LABELS
.
from the error message now,I think syntax error may emmit by the
parser,parser error make it hard to get the really condition such as the
second
can we make a cross reference from doc 4.4.1(
http://www.postgresql.org/docs/devel/static/sql-syntax-lexical.html#SQL-SYNTAX-IDENTIFIERS
)
to
doc 7.3.2 (
http://www.postgresql.org/docs/devel/static/queries-select-lists.html#QUERIES-COLUMN-LABELS
)
*to mention that “AS” can make a key word to be a i
21.02.2013 21:25, Jeff Janes пишет:
On Wed, Feb 20, 2013 at 5:42 AM, Claude Speed wrote:
Hi all,
Postgresql 9.2.3 is processing my query is much longer than Postgresql
9.1.8:
Postgresql 9.1.8 - 2292 ms
Postgresql 9.2.3 - 163336 ms
I provided my query in attach and the database dump too,
this
The following bug has been logged on the website:
Bug reference: 7899
Logged by: jov
Email address: am...@amutu.com
PostgreSQL version: 9.1.3
Operating system: CentOS 6
Description:
xxx=# select 2 from (select 1 as end) t;
?column?
--
2
(1 row)
x
The following bug has been logged on the website:
Bug reference: 7900
Logged by: tan hong wei
Email address: tiyuk...@126.com
PostgreSQL version: 9.1.4
Operating system: cent os 5.5
Description:
1 create a db session s1,and execue sql:create table a(i int);
2 kill -
Jeff Janes writes:
> The slowness was introduced with this:
> Use parameterized paths to generate inner indexscans more flexibly.
Try increasing from_collapse_limit to 11 or more.
I'm not exactly sure why the param-path patch might have changed this
behavior, but in any case the collapse lim
The following bug has been logged on the website:
Bug reference: 7902
Logged by: Jeff Frost
Email address: j...@pgexperts.com
PostgreSQL version: 9.2.3
Operating system: Ubuntu 12.04
Description:
While doing acceptance testing on a new Ubuntu 12.04 PostgreSQL server
r