pgsql: Clean up after TAP tests in oid2name and vacuumlo.

2018-09-04 Thread Tom Lane
Clean up after TAP tests in oid2name and vacuumlo. Oversights in commits 1aaf532de and bfea331a5. Unlike the case for traditional-style REGRESS tests, pgxs.mk doesn't have any builtin support for TAP tests, so it doesn't realize it should remove tmp_check/. Maybe we should build some actual pgxs

Re: pgsql: Clean up after TAP tests in oid2name and vacuumlo.

2018-09-04 Thread Michael Paquier
On Tue, Sep 04, 2018 at 02:52:07PM +, Tom Lane wrote: > Clean up after TAP tests in oid2name and vacuumlo. > > Oversights in commits 1aaf532de and bfea331a5. Unlike the case for > traditional-style REGRESS tests, pgxs.mk doesn't have any builtin support > for TAP tests, so it doesn't realize

Re: pgsql: Clean up after TAP tests in oid2name and vacuumlo.

2018-09-04 Thread Tom Lane
Michael Paquier writes: > On Tue, Sep 04, 2018 at 02:52:07PM +, Tom Lane wrote: >> Oversights in commits 1aaf532de and bfea331a5. Unlike the case for >> traditional-style REGRESS tests, pgxs.mk doesn't have any builtin support >> for TAP tests, so it doesn't realize it should remove tmp_check

pgsql: Fully enforce uniqueness of constraint names.

2018-09-04 Thread Tom Lane
Fully enforce uniqueness of constraint names. It's been true for a long time that we expect names of table and domain constraints to be unique among the constraints of that table or domain. However, the enforcement of that has been pretty haphazard, and it missed some corner cases such as creating

pgsql: Fully enforce uniqueness of constraint names.

2018-09-04 Thread Tom Lane
Fully enforce uniqueness of constraint names. It's been true for a long time that we expect names of table and domain constraints to be unique among the constraints of that table or domain. However, the enforcement of that has been pretty haphazard, and it missed some corner cases such as creating

pgsql: Improve some error message strings and errcodes

2018-09-04 Thread Michael Paquier
Improve some error message strings and errcodes This makes a bit less work for translators, by unifying error strings a bit more with what the rest of the code does, this time for three error strings in autoprewarm and one in base backup code. After some code review of slot.c, some file-access er

Re: pgsql: Clean up after TAP tests in oid2name and vacuumlo.

2018-09-04 Thread Michael Paquier
On Tue, Sep 04, 2018 at 01:41:53PM -0400, Tom Lane wrote: > It's really accidental that $(pg_regress_clean_files) happens to be a > superset of what the TAP tests need to have cleaned; we shouldn't build > that assumption in further. Fine for me. > If we're gonna do anything here, I think it'd be

Re: pgsql: Clean up after TAP tests in oid2name and vacuumlo.

2018-09-04 Thread Tom Lane
Michael Paquier writes: > Okay, I don't want to create a dependency between REGRESS and > HAVE_TAP_TESTS either, but modules specifying both should be able to > trigger both regressions and tap tests. Agreed ... > So I would be inclined to > create two new rules, say check-regress and installche

Re: pgsql: Clean up after TAP tests in oid2name and vacuumlo.

2018-09-04 Thread Michael Paquier
On Tue, Sep 04, 2018 at 03:16:55PM -0400, Tom Lane wrote: > Why would we invent a different target name? I was thinking something > roughly like > > check: submake $(REGRESS_PREP) > ifdef REGRESS > $(pg_regress_check) $(REGRESS_OPTS) $(REGRESS) > endif > ifdef TAP_TESTS > $(prove_chec

pgsql: docs: improve AT TIME ZONE description

2018-09-04 Thread Bruce Momjian
docs: improve AT TIME ZONE description The previous description was unclear. Also add a third example, change use of time zone acronyms to more verbose descriptions, and add a mention that using 'time' with AT TIME ZONE uses the current time zone rules. Backpatch-through: 9.3 Branch -- REL

pgsql: docs: improve AT TIME ZONE description

2018-09-04 Thread Bruce Momjian
docs: improve AT TIME ZONE description The previous description was unclear. Also add a third example, change use of time zone acronyms to more verbose descriptions, and add a mention that using 'time' with AT TIME ZONE uses the current time zone rules. Backpatch-through: 9.3 Branch -- REL

pgsql: docs: improve AT TIME ZONE description

2018-09-04 Thread Bruce Momjian
docs: improve AT TIME ZONE description The previous description was unclear. Also add a third example, change use of time zone acronyms to more verbose descriptions, and add a mention that using 'time' with AT TIME ZONE uses the current time zone rules. Backpatch-through: 9.3 Branch -- REL

pgsql: docs: improve AT TIME ZONE description

2018-09-04 Thread Bruce Momjian
docs: improve AT TIME ZONE description The previous description was unclear. Also add a third example, change use of time zone acronyms to more verbose descriptions, and add a mention that using 'time' with AT TIME ZONE uses the current time zone rules. Backpatch-through: 9.3 Branch -- REL

pgsql: docs: improve AT TIME ZONE description

2018-09-04 Thread Bruce Momjian
docs: improve AT TIME ZONE description The previous description was unclear. Also add a third example, change use of time zone acronyms to more verbose descriptions, and add a mention that using 'time' with AT TIME ZONE uses the current time zone rules. Backpatch-through: 9.3 Branch -- REL

pgsql: docs: improve AT TIME ZONE description

2018-09-04 Thread Bruce Momjian
docs: improve AT TIME ZONE description The previous description was unclear. Also add a third example, change use of time zone acronyms to more verbose descriptions, and add a mention that using 'time' with AT TIME ZONE uses the current time zone rules. Backpatch-through: 9.3 Branch -- mas

pgsql: docs: improve AT TIME ZONE description

2018-09-04 Thread Bruce Momjian
docs: improve AT TIME ZONE description The previous description was unclear. Also add a third example, change use of time zone acronyms to more verbose descriptions, and add a mention that using 'time' with AT TIME ZONE uses the current time zone rules. Backpatch-through: 9.3 Branch -- REL