| From: | Jakub Wartak <Jakub(dot)Wartak(at)tomtom(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | RE: pg_preadv() and pg_pwritev() |
| Date: | 2020-12-21 07:25:50 |
| Message-ID: | VI1PR0701MB6960F6D42E6B4727A7B45F66F6C00@VI1PR0701MB6960.eurprd07.prod.outlook.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > I'm drawing a blank on trivial candidate uses for preadv(), without
> > infrastructure from later patches.
>
> Can't immediately think of something either.
This might be not that trivial , but maybe acquire_sample_rows() from analyze.c ?
Please note however there's patch https://www.postgresql.org/message-id/20201109180644.GJ16415%40tamriel.snowman.net ( https://commitfest.postgresql.org/30/2799/ ) for adding fadvise, but maybe those two could be even combined so you would be doing e.g. 16x fadvise() and then grab 8 pages in one preadv() call ? I'm find unlikely however that preadv give any additional performance benefit there after having fadvise, but clearly a potential place to test.
-J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bharath Rupireddy | 2020-12-21 07:42:07 | Re: New Table Access Methods for Multi and Single Inserts |
| Previous Message | Masahiko Sawada | 2020-12-21 07:02:29 | Dependency isn't created between extension and schema |