diff options
author | Tom Lane | 2019-02-17 17:37:32 +0000 |
---|---|---|
committer | Tom Lane | 2019-02-17 17:37:32 +0000 |
commit | 1f29a1d2288a10282fa0dc4cd53000f4d660c7d6 (patch) | |
tree | c01c72c860b2e7f495db9097ca882c4755b968e5 /doc | |
parent | 0c2dcb9332ef6d25b4adf8ca918a7083ebb5dcdc (diff) |
Fix CREATE VIEW to allow zero-column views.
We should logically have allowed this case when we allowed zero-column
tables, but it was overlooked.
Although this might be thought a feature addition, it's really a bug
fix, because it was possible to create a zero-column view via
the convert-table-to-view code path, and then you'd have a situation
where dump/reload would fail. Hence, back-patch to all supported
branches.
Arrange the added test cases to provide coverage of the related
pg_dump code paths (since these views will be dumped and reloaded
during the pg_upgrade regression test). I also made them test
the case where pg_dump has to postpone the view rule into post-data,
which disturbingly had no regression coverage before.
Report and patch by Ashutosh Sharma (test case by me)
Discussion: https://postgr.es/m/CAE9k0PkmHdeSaeZt2ujnb_cKucmK3sDDceDzw7+d5UZoNJPYOg@mail.gmail.com
Diffstat (limited to 'doc')
0 files changed, 0 insertions, 0 deletions