| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Issue with cancel_before_shmem_exit while searching to remove a particular registered exit callbacks |
| Date: | 2020-09-07 15:20:21 |
| Message-ID: | 1671027.1599492021@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Michael Paquier <michael(at)paquier(dot)xyz> writes:
> Is there still something that needs to absolutely be done here knowing
> that we have bab1500 that got rid of the root issue? Can the CF entry
> be marked as committed?
I think there is agreement that we're not going to change
cancel_before_shmem_exit's restriction to only allow LIFO popping.
So we should improve its comment to explain why. The other thing
that seems legitimately on-the-table for this CF entry is whether
we should change cancel_before_shmem_exit to complain, rather than
silently do nothing, if it fails to pop the stack. Bharath's
last patchset proposed to add an elog(DEBUG3) complaint, which
seems to me to be just about entirely useless. I'd make it an
ERROR, or maybe an Assert.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrey M. Borodin | 2020-09-07 15:24:18 | Re: Yet another fast GiST build |
| Previous Message | John Naylor | 2020-09-07 15:16:28 | Re: [doc] minor wording improvement in a couple of places |