| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robins Tharakan <tharakan(at)gmail(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Szymon Guz <mabewlun(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Add more regression tests for CREATE OPERATOR |
| Date: | 2013-06-27 14:52:20 |
| Message-ID: | 21262.1372344740@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robins Tharakan <tharakan(at)gmail(dot)com> writes:
> 2. Should I assume that all database objects that get created, need to be
> dropped explicitly? Or is this point specifically about ROLES?
It's about any global objects (that wouldn't get dropped by dropping the
regression database). As far as local objects go, there are benefits to
leaving them around, particularly if they present interesting test cases
for pg_dump/pg_restore.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2013-06-27 14:52:22 | Re: Add more regression tests for dbcommands |
| Previous Message | Peter Eisentraut | 2013-06-27 14:40:36 | Re: FILTER for aggregates [was Re: Department of Redundancy Department: makeNode(FuncCall) division] |