Hello Rajkumar,
On Tue, Nov 14, 2017 at 2:22 PM, Rajkumar Raghuwanshi
<rajkumar.raghuwan...@enterprisedb.com> wrote:
> On Tue, Nov 14, 2017 at 11:46 AM, Beena Emerson <memissemer...@gmail.com>
> wrote:
>>
>> PFA the updated patches.
>
>
> Hi,
>
>
%40lab.ntt.co.jp
[2]
https://www.postgresql.org/message-id/df609168-b7fd-4c0b-e9b2-6e398d411e27%40lab.ntt.co.jp
--
Beena Emerson
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
0001-Implement-runtime-partiton-pruning_v3.patch
Description: Binary data
On Tue, Nov 14, 2017 at 6:27 PM, David Rowley
<david.row...@2ndquadrant.com> wrote:
> On 14 November 2017 at 19:16, Beena Emerson <memissemer...@gmail.com> wrote:
>> PFA the updated patches.
>
> Hi Beena,
>
> Thanks for working on this. I've had a look at the
r: ((a >= 4) AND (a <= 5) AND (a = 4))
(3 rows)
postgres=# explain execute ab_q1 (4);
QUERY PLAN
--------
Append (cost=0.00..99.10 rows=1 width=8)
-> Seq Scan on ab_a4 (cost=0.00..49.55 rows=1 width=8)
Filter: ((a >= 4) AND (a <= 5) AND (a = $1))
(3 rows)
--
Beena Emerson
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Hello,
On Wed, Nov 29, 2017 at 7:11 AM, Michael Paquier
<michael.paqu...@gmail.com> wrote:
> On Wed, Nov 15, 2017 at 3:53 PM, Beena Emerson <memissemer...@gmail.com>
> wrote:
>> Thank you for your suggestion. I am looking into this and will post a
>> patch soon.
&
Hello Robert,
On Sat, Dec 2, 2017 at 12:34 AM, Robert Haas <robertmh...@gmail.com> wrote:
> On Fri, Dec 1, 2017 at 6:20 AM, Beena Emerson <memissemer...@gmail.com> wrote:
>> David Q1:
>> postgres=# explain analyse e
when the
> plan is going to be used multiple times with different parameters, so
> we really don't want to repeat any work that we don't have to here.
>
I agree. It would be better to avoid building the structure during execution.
PFA the updated patch.
--
Beena Emerson
Enterpr
PFA the updated patches.
On Tue, Nov 14, 2017 at 11:45 AM, Beena Emerson <memissemer...@gmail.com> wrote:
> Hello Amul,
>
> Thank you for reviewing.
>
> On Fri, Nov 10, 2017 at 4:33 PM, amul sul <sula...@gmail.com> wrote:
>> On Thu, Nov 9, 2017 at 4:48 PM, Beena
Hello Amul,
Thank you for reviewing.
On Fri, Nov 10, 2017 at 4:33 PM, amul sul <sula...@gmail.com> wrote:
> On Thu, Nov 9, 2017 at 4:48 PM, Beena Emerson <memissemer...@gmail.com> wrote:
>> Hello all,
>>
>> Here is the updated patch which is rebased over v10
xecution time: 0.111 ms
I am still working on the patch to add more comments and regression
tests but comments on the code is welcome.
[1]https://www.postgresql.org/message-id/df609168-b7fd-4c0b-e9b2-6e398d411e27%40lab.ntt.co.jp
--
Beena Emerson
EnterpriseDB: http://www.enterprisedb.com
T
On Wed, Dec 6, 2017 at 1:21 PM, David Rowley
<david.row...@2ndquadrant.com> wrote:
> On 2 December 2017 at 08:04, Robert Haas <robertmh...@gmail.com> wrote:
>> On Fri, Dec 1, 2017 at 6:20 AM, Beena Emerson <memissemer...@gmail.com>
>> wrote:
>>> David Q
Hello,
On Thu, Dec 7, 2017 at 12:52 PM, Beena Emerson <memissemer...@gmail.com> wrote:
>
> 1. Only runtime pruning - David's case1
> explain analyse execute ab_q1 (2,3);
>
Hello David,
On Thu, Dec 7, 2017 at 4:07 PM, David Rowley
<david.row...@2ndquadrant.com> wrote:
> On 7 December 2017 at 20:22, Beena Emerson <memissemer...@gmail.com> wrote:
>> PFA the updated patch.
>
> Hi Beena,
>
> Thanks for updating this.
>
> Can
Hello Robert,
Thank you for the comments. I have started working on it.
On Fri, Dec 8, 2017 at 9:27 PM, Robert Haas <robertmh...@gmail.com> wrote:
> On Thu, Dec 7, 2017 at 2:22 AM, Beena Emerson <memissemer...@gmail.com> wrote:
>> I have added the partition quals that
On Tue, Dec 12, 2017 at 4:57 PM, Beena Emerson <memissemer...@gmail.com> wrote:
> Hello Robert,
> Thank you for the comments. I have started working on it.
>
> On Fri, Dec 8, 2017 at 9:27 PM, Robert Haas <robertmh...@gmail.com> wrote:
>> On Thu, Dec 7, 2017 at 2:22
Hello,
On Fri, Dec 8, 2017 at 3:37 AM, David Rowley
<david.row...@2ndquadrant.com> wrote:
> On 7 December 2017 at 23:56, Beena Emerson <memissemer...@gmail.com> wrote:
>> Currently Amit's v13 patches do not apply on the HEAD and I was
>> working on 487a0c1518af2f3ae2d
Hello Jesper,
On Tue, Dec 12, 2017 at 4:04 PM, Jesper Pedersen
<jesper.peder...@redhat.com> wrote:
> Hi Beena,
>
> On 12/07/2017 02:22 AM, Beena Emerson wrote:
>>
>> I have added the partition quals that are used for pruning.
>>
>> PFA the updated patch
Hello David,
On Thu, Dec 21, 2017 at 2:31 PM, David Rowley
<david.row...@2ndquadrant.com> wrote:
> On 19 December 2017 at 21:54, Beena Emerson <memissemer...@gmail.com> wrote:
> The problem is down to the logic in choose_custom_plan() only choosing
> a generic pla
Hello,
On Thu, Dec 21, 2017 at 6:01 PM, David Rowley
<david.row...@2ndquadrant.com> wrote:
> On 21 December 2017 at 23:51, Beena Emerson <memissemer...@gmail.com> wrote:
>> On Thu, Dec 21, 2017 at 2:31 PM, David Rowley
>> <david.row...@2ndquadrant.com> wrote:
Hi,
The mail was accidently sent before I could complete.
On Tue, Jan 9, 2018 at 2:24 PM, Beena Emerson <memissemer...@gmail.com> wrote:
> Hello,
>
> The pruning does not work well with char type:
>
> Case 2: Case with optimizer pruning
> drop table ab_c;
> create ta
(a >= $1) AND (a <= $2) AND (b = ANY ('{3,2}'::integer[])))
-> Seq Scan on abc_a3_b2 (never executed)
Filter: ((a >= $1) AND (a <= $2) AND (b = ANY ('{3,2}'::integer[])))
-> Seq Scan on abc_a3_b3 (never executed)
Filter: ((a >= $1) AND (a <= $2) AND (b
dditional
features you added like optimizing the pruning rescan. I will try and
post the patch tomorrow.
If there is more suggestions, you can give it over that; otherwise it
seems like duplicating efforts.
--
Beena Emerson
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Hello,
On Thu, Dec 21, 2017 at 6:30 PM, David Rowley
<david.row...@2ndquadrant.com> wrote:
> On 22 December 2017 at 01:43, Beena Emerson <memissemer...@gmail.com> wrote:
>>> I wonder if Robert understands the extent of the problem. The patch
>>> will be use
* FROM
prun_test_part WHERE sal < (SELECT sal FROM prun_test_part WHERE sal =
200);
server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
The connection to the server was lost. Attempting reset: Failed.
--
Been
Hello,
On Mon, 10 Sep 2018, 19:33 Amit Kapila, wrote:
> On Mon, Sep 10, 2018 at 1:12 PM Haribabu Kommi
> wrote:
> >
> > On Wed, Sep 5, 2018 at 2:04 PM Haribabu Kommi
> wrote:
> >>
> > pg_stat_get_tuples_hot_updated and others:
> > /*
> > * Counter tuples_hot_updated stores number of hot
/regress/results/inherit.out
>
With Amit's v46 patch, the following query in partition_prune was
crashing during make check.
explain (analyze, costs off, summary off, timing off) execute ab_q1 (2, 2, 3);
--
Beena Emerson
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Hi David,
On Wed, Apr 4, 2018 at 7:57 AM, David Rowley
<david.row...@2ndquadrant.com> wrote:
> On 4 April 2018 at 05:50, Beena Emerson <memissemer...@gmail.com> wrote:
>> With Amit's v46 patch, the following query in partition_prune was
>> crashing during make check.
| | plain |
|
c2 | integer | | | | plain |
|
Access method: heap
--
Beena Emerson
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
28 matches
Mail list logo
