| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, hackers(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] psql & regress tests |
| Date: | 1999-11-19 00:58:40 |
| Message-ID: | 199911190058.TAA19713@candle.pha.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> >> * Since no one has picked up on my idea to run the tests directly on the
> >> backend, I will keep reiterating this idea until someone shuts me up
>
> > Running the backend standalone does not use locking with other backends,
> > so it is dangerous.
>
> It wouldn't be particularly "dangerous" if we assume that no one else is
> accessing the regression database. What it *would* be is less useful at
> catching problems. Standalone mode wouldn't test the cross-backend
> interlocking code at all.
Any modifications to shared pg_ tables would be a problem. Also, pg_log
and pg_variable locking is not happening in there either, is it?
--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 1999-11-19 01:12:18 | Getting OID in psql of recent insert |
| Previous Message | Jan Wieck | 1999-11-19 00:57:30 | Re: [HACKERS] psql & regress tests |