| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Name for new VACUUM |
| Date: | 2001-08-02 20:40:01 |
| Message-ID: | 13772.996784801@sss.pgh.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:
> I was thinking about our new version of vacuum. I think it should be
> called VACUUM NOLOCK to make it clear when you should use it, and we can
> keep our ordinary VACUUM the same.
I really don't understand why you're so hot to avoid changing the
default behavior of VACUUM. Name me even one user who *likes* the
current behavior (ie, VACUUM grabs exclusive lock)? IMHO the default
behavior *should* change. Otherwise you're just forcing people to
update their cron scripts, which they wouldn't need to touch if we
do it the way I want.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-08-02 20:58:50 | Re: Revised Patch to allow multiple table locks in "Unison" |
| Previous Message | Tom Lane | 2001-08-02 20:28:03 | Re: Patch for Improved Syntax Error Reporting |