| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pageinspect option to forgo buffer locking? |
| Date: | 2017-11-09 17:51:25 |
| Message-ID: | CAH2-Wzkv5hD7SYpVSuLSx4GMZqopY1=21iKQi4SrMJiT4Q7P3Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Nov 9, 2017 at 9:49 AM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> Currently the locking in get_raw_page_internal() prevents that. If it's
> an option defaulting to off, I don't see why we couldn't allow that to
> skip locking the page's contents. Obviously you can get corrupted
> contents that way, but we already allow to pass arbitrary stuff to
> heap_page_items(). Since pinning wouldn't be changed, there's no danger
> of the page being moved out from under us.
+1. I've done things like this before myself.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2017-11-09 17:53:17 | Re: libpq connection strings: control over the cipher suites? |
| Previous Message | Andres Freund | 2017-11-09 17:49:11 | pageinspect option to forgo buffer locking? |