| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | Jesper Pedersen <jesper(dot)pedersen(at)redhat(dot)com>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Write Ahead Logging for Hash Indexes |
| Date: | 2017-03-10 14:34:46 |
| Message-ID: | CA+TgmoZwWqivPZiyVTZvrrJ0QsjddDbjK5wVyLtfOZ82vr58cg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Mar 10, 2017 at 8:02 AM, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
> I was thinking that we will use REGBUF_NO_IMAGE flag as is used in
> XLOG_HEAP2_VISIBLE record for heap buffer, that will avoid any extra
> I/O and will make it safe as well. I think that makes registering the
> buffer safe without setting LSN for XLOG_HEAP2_VISIBLE record.
Hmm, yeah, that might work, though I would probably want to spend some
time studying the patch and thinking about it before deciding for
sure.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Korotkov | 2017-03-10 14:45:43 | Re: Re: proposal - psql: possibility to specify sort for describe commands, when size is printed |
| Previous Message | Alexander Korotkov | 2017-03-10 14:29:16 | Re: Index usage for elem-contained-by-const-range clauses |