From: | Dave Page <dpage(at)postgresql(dot)org> |
---|---|
To: | Stephen Denne <Stephen(dot)Denne(at)datamail(dot)co(dot)nz> |
Cc: | pgadmin-support(at)postgresql(dot)org |
Subject: | Re: 1.6RC2 explain analyze rollback bug |
Date: | 2006-11-10 10:28:14 |
Message-ID: | 4554543E.30504@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
Stephen Denne wrote:
> Using downloaded pgAdmin III 1.6RC2 on windows xp sp2, connecting to a local 8.1.4 PostgreSQL database, I had a query in an SQL window which I was able to run, or explain, but when I used the Query Explain Options menu to turned on analyze, and hit F7, I received an error.
>
> I've managed to find a simple reproducible example…
>
> Open a new Query tool, paste the following as a single line, including the end of line comment, but with no trailing line break:
>
> SELECT * from pg_stat_activity WHERE datname = 'postgres' --
>
> This can be run or explained, but not explain & analyzed. The following error is given:
>
> ERROR: syntax error at or near "ROLLBACK"
> SQL state: 42601
> Character: 87
>
> If a line break is added at the end, or the end of line comment is removed, or a semi colon is placed at the end of the statement, then explain analyze works as expected. Line breaks can be placed anywhere else without affecting the behaviour, but the behaviour is seen if there is no line break after --
Thanks, I've committed a fix for this issue.
Regards, Dave.
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Pundt | 2006-11-10 13:14:52 | Hard time compiling from source |
Previous Message | Dave Page | 2006-11-10 09:55:27 | Re: edit grid: issues involving marking, selecting, |