Re: Run-time pruning for ModifyTable - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: Run-time pruning for ModifyTable
Date
Msg-id CA+hUKG+BvjrnMPVDevGrJfg=zHo1a6ZrnLfx__koULsv8BULKg@mail.gmail.com
Whole thread Raw
In response to Re: Run-time pruning for ModifyTable  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: Run-time pruning for ModifyTable
List pgsql-hackers
On Thu, Sep 12, 2019 at 10:10 AM Alvaro Herrera
<alvherre@2ndquadrant.com> wrote:
> Here's a rebased version of this patch (it had a trivial conflict).

Hi, FYI partition_prune.sql currently fails (maybe something to do
with commit d52eaa09?):

 where s.a = $1 and s.b = $2 and s.c = (select 1);
 explain (costs off) execute q (1, 1);
                           QUERY PLAN
----------------------------------------------------------------
+----------------------------------------------------
  Append
    InitPlan 1 (returns $0)
      ->  Result
-   Subplans Removed: 1
    ->  Seq Scan on p1
-         Filter: ((a = $1) AND (b = $2) AND (c = $0))
+         Filter: ((a = 1) AND (b = 1) AND (c = $0))
    ->  Seq Scan on q111
-         Filter: ((a = $1) AND (b = $2) AND (c = $0))
+         Filter: ((a = 1) AND (b = 1) AND (c = $0))
    ->  Result
-         One-Time Filter: ((1 = $1) AND (1 = $2) AND (1 = $0))
-(10 rows)
+         One-Time Filter: (1 = $0)
+(9 rows)

 execute q (1, 1);
  a | b | c



pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: pause recovery if pitr target not reached
Next
From: Michael Paquier
Date:
Subject: Re: TAP tests aren't using the magic words for Windows file access