diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2020-09-13 12:51:21 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2020-09-13 12:51:21 -0400 |
| commit | 1371a1e4161a25a128b666109ac5a9d449da982a (patch) | |
| tree | c5f4affa110c52532c93f5f70c55435f1a09a517 /src/backend/access/gist/gist.c | |
| parent | 6a8f6aee0cbea617df90fe3b715d6dd73e0f8c04 (diff) | |
| download | postgresql-1371a1e4161a25a128b666109ac5a9d449da982a.tar.gz postgresql-1371a1e4161a25a128b666109ac5a9d449da982a.zip | |
Use the properly transformed RangeVar for expandTableLikeClause().
transformCreateStmt() adjusts the transformed statement's RangeVar
to specify the target schema explicitly, for the express reason
of making sure that auxiliary statements derived by parse
transformation operate on the right table. But the refactoring
I did in commit 502898192 got this wrong and passed the untransformed
RangeVar to expandTableLikeClause(). This could lead to assertion
failures or weird misbehavior if the wrong table was accessed.
Per report from Alexander Lakhin. Like the previous patch, back-patch
to all supported branches.
Discussion: https://postgr.es/m/05051f9d-b32b-cb35-6735-0e9f2ab86b5f@gmail.com
Diffstat (limited to 'src/backend/access/gist/gist.c')
0 files changed, 0 insertions, 0 deletions