diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2010-10-02 20:02:52 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2010-10-02 20:02:52 -0400 |
| commit | d8014f9a7f9ec848890296d7c01dbf7b2d70fc1b (patch) | |
| tree | c382029704389ef26cbedfc9b157f07f75c6352d /src/backend/access/gist | |
| parent | 61318f38c0999e828d34230c3ea57eb24c49ceba (diff) | |
| download | postgresql-d8014f9a7f9ec848890296d7c01dbf7b2d70fc1b.tar.gz postgresql-d8014f9a7f9ec848890296d7c01dbf7b2d70fc1b.zip | |
Behave correctly if INSERT ... VALUES is decorated with additional clauses.
In versions 8.2 and up, the grammar allows attaching ORDER BY, LIMIT,
FOR UPDATE, or WITH to VALUES, and hence to INSERT ... VALUES. But the
special-case code for VALUES in transformInsertStmt() wasn't expecting any
of those, and just ignored them, leading to unexpected results. Rather
than complicate the special-case path, just ensure that the presence of any
of those clauses makes us treat the query as if it had a general SELECT.
Per report from Hitoshi Harada.
Diffstat (limited to 'src/backend/access/gist')
0 files changed, 0 insertions, 0 deletions