From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
---|---|
To: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 12:11:01 |
Message-ID: | CAA4eK1+-kiNXzux4uoiyQr-s3HYgY=eMqovEzYPjrq_0G4-rgw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
On Sun, Jun 17, 2018 at 9:22 PM, Andrew Gierth
<andrew(at)tao11(dot)riddles(dot)org(dot)uk> wrote:
>>>>>> "Tom" == Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
>
> Tom> 2. Although _bt_killitems doesn't WAL-log its setting of kill
> Tom> bits, those bits could propagate to the standby anyway, as a
> Tom> result of a subsequent WAL action on the index page that gets a
> Tom> full-page image added.
>
> 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? Now, if the user has
enabled wal_log_hints on the master, it could save time from scanning
many dead tuples on standby.
--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Bruno Lavoie | 2018-06-18 12:31:32 | Re: Failed rpm package signature checks with reposync |
Previous Message | Fabio Pardi | 2018-06-18 10:38:35 | pgbench on pglogical: bandwidth usage |
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2018-06-18 12:26:36 | Re: Concurrency bug in UPDATE of partition-key |
Previous Message | Jeevan Chalke | 2018-06-18 11:40:12 | Re: Server crashed with TRAP: FailedAssertion("!(parallel_workers > 0)" when partitionwise_aggregate true. |