| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Luca Ferrari <fluca1978(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: could not read block 0 in file : read only 0 of 8192 bytes when doing nasty on immutable index function |
| Date: | 2018-08-02 20:00:16 |
| Message-ID: | CAH2-Wzn_4+FMDkdcy=iQqW28Y2aeCmKeZo947Wed4t0o4oLBxQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-general |
On Tue, Jul 31, 2018 at 9:00 PM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> I don't think that's particularly relevant. We should always register an
> invalidation before the relevant CommandCounterIncrement(), because that
> is what makes catalog changes visible, and therefore requires
> registering invalidations for coherency.
Fair enough. How about the attached revision?
--
Peter Geoghegan
| Attachment | Content-Type | Size |
|---|---|---|
| v2-0001-Add-table-relcache-invalidation-to-index-builds.patch | application/octet-stream | 1.8 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2018-08-02 20:05:37 | Re: could not read block 0 in file : read only 0 of 8192 bytes when doing nasty on immutable index function |
| Previous Message | Michael Paquier | 2018-08-02 19:07:13 | Re: BUG #15182: Canceling authentication due to timeout aka Denial of Service Attack |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2018-08-02 20:05:37 | Re: could not read block 0 in file : read only 0 of 8192 bytes when doing nasty on immutable index function |
| Previous Message | Adrian Klaver | 2018-08-02 18:47:25 | Re: List user who have access to schema |