| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, Maksim Milyutin <milyutinma(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Slow planning time for simple query |
| Date: | 2018-06-18 14:20:19 |
| Message-ID: | 12843.1529331619@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> writes:
> On Sun, Jun 17, 2018 at 9:22 PM, Andrew Gierth
> <andrew(at)tao11(dot)riddles(dot)org(dot)uk> wrote:
>> That's OK as long as we're ignoring those hints on the standby.
> What if we don't ignore those hints on standby for a specific case
> like the one in get_actual_variable_range?
Yeah, that's the same idea I suggested upthread. Andrew shot down
my first thought (correctly I think) but the second one still seems
feasible.
> Now, if the user has
> enabled wal_log_hints on the master, it could save time from scanning
> many dead tuples on standby.
We should have the standby set the hint bits for itself, rather than
relying on wal_log_hints.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sherrylyn Branchaw | 2018-06-18 15:34:11 | What to do when dynamic shared memory control segment is corrupt |
| Previous Message | Adrian Klaver | 2018-06-18 13:53:14 | Re: Clarifying "timestamp with time zone" |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2018-06-18 14:26:43 | Re: [Proposal] Table-level Transparent Data Encryption (TDE) and Key Management Service (KMS) |
| Previous Message | Joe Conway | 2018-06-18 14:12:28 | Re: [Proposal] Table-level Transparent Data Encryption (TDE) and Key Management Service (KMS) |