Hi Amit,
On 2017/07/24 14:09, Amit Khandekar wrote:
>>> On 2017/07/10 14:15, Etsuro Fujita wrote:
>>> Another thing I noticed is the error handling in ExecWithCheckOptions; it
>>> doesn't take any care for partition tables, so the column description in
>>> the error message for WCO_VIEW_CHECK is b
On Wed, Jul 19, 2017 at 05:01:31PM -0400, Tom Lane wrote:
> Ashutosh Sharma writes:
> > Here are the list of macros and variables from 'intrpvar.h' file that
> > are just defined in perl module but not in plperl on Windows,
>
> > #ifdef PERL_USES_PL_PIDSTATUS
> > PERLVAR(I, pidstatus, HV *)
On Tue, Jul 18, 2017 at 01:04:10PM -0700, Andres Freund wrote:
> Ok, I'll flesh out the patch till Thursday. But I do think we're going
> to have to do something about the back branches, too.
This PostgreSQL 10 open item is past due for your status update. Kindly send
a status update within 24 h
On 13 July 2017 at 22:39, Amit Khandekar wrote:
> Attached is a WIP patch (make_resultrels_ordered.patch) that generates
> the result rels in canonical order. This patch is kept separate from
> the update-partition-key patch, and can be applied on master branch.
Attached update-partition-key_v13.
>> On 2017/07/10 14:15, Etsuro Fujita wrote:
>> Another thing I noticed is the error handling in ExecWithCheckOptions; it
>> doesn't take any care for partition tables, so the column description in
>> the error message for WCO_VIEW_CHECK is built using the partition table's
>> rowtype, not the root
On Fri, Jul 21, 2017 at 10:39 PM, Tom Lane wrote:
> Ashutosh Bapat writes:
>> On Fri, Jul 21, 2017 at 10:55 AM, Kyotaro HORIGUCHI
>> wrote:
>>> The attached patch differs only in this point.
>
>> +1. The patch looks good to me.
>
> Pushed with a couple additional changes: we'd all missed that th
On Sat, Jul 22, 2017 at 8:04 AM, Stephen Frost wrote:
> Masahiko, all,
>
> * Masahiko Sawada (sawada.m...@gmail.com) wrote:
>> On Tue, Jul 18, 2017 at 1:28 PM, Stephen Frost wrote:
>> > Masahiko, Michael,
>> >
>> > * Masahiko Sawada (sawada.m...@gmail.com) wrote:
>> >> > This is beginning to shap
On 2017/07/21 19:16, Etsuro Fujita wrote:
On 2017/07/20 11:21, Etsuro Fujita wrote:
On 2017/07/19 23:36, Tom Lane wrote:
Please put the responsibility of doing const-expression simplification
in these cases somewhere closer to where the problem is being created.
It would be reasonable that it
On Fri, Jul 21, 2017 at 10:31 PM, Peter Geoghegan wrote:
> On Wed, Aug 17, 2016 at 7:54 PM, Claudio Freire
> wrote:
>> The attached patch tries to maintain the initial status of B-Tree
>> indexes, which are created with equal-key runs in physical order,
>> during the whole life of the B-Tree, an
On Sun, Jul 23, 2017 at 8:32 AM, Tom Lane wrote:
> Meanwhile, it's still pretty unclear what happened yesterday on
> culicidae.
That failure is indeed baffling. The only code that inserts
(HASH_ENTER[_NULL]) into PredicateLockTargetHash:
1. CreatePredicateLock(). I would be a bug if that ever
Hello,
I changed the test to run for 6 hours at a time regardless of number of
transactions. I also changed the du command to only look at the database
(previously wal logs were included). This is the clearest indication of
the problem I have been able to produce.
Again, this is with 128 cli
I wrote:
> Dima Pavlov writes:
>> That's my first patch so I will be grateful for constructive criticism.
> I think it would be better to do this in the planner, see specifically
> eval_const_expressions.
BTW, currently eval_const_expressions doesn't know anything about
ScalarArrayOpExpr, but th
Dima Pavlov writes:
> The problem was discussed on stackoverflow:
> https://stackoverflow.com/questions/45061966/index-usage-with-single-item-anyarray
Usually, we're not very happy with submissions that reference external
pages for justification; we like to have all the relevant material in our
m
Andrew Dunstan writes:
> It turns out I was wrong about the problem jacana has been having with
> the pg_ctl tests hanging. The problem was not the use of select as a
> timeout mechanism, although I think the change to using
> Time::Hires::usleep() is correct and shouldn't be reverted.
> The prob
Hello,
The problems I tried to solve here:
1. Improve perfomance for index search ANY(ARRAY[...]) condition with
single item
2. I saw tons of users code like: if len(array) == 1: sql +=
'{}'.format(array[0]) else: sql += 'ANY(ARRAY[{}])'.format(array)
So there will be less lines of code and it wil
In the last week, I focus on
1) Creating an independent skip list data structure and related interfaces.
Now it has only two levels so that I don't have to modify too much existing
code. But it is easy to be transformed into the data structure with any number
of levels if necessary. Unfortunatel
It turns out I was wrong about the problem jacana has been having with
the pg_ctl tests hanging. The problem was not the use of select as a
timeout mechanism, although I think the change to using
Time::Hires::usleep() is correct and shouldn't be reverted.
The problem is command_like's use of redi
17 matches
Mail list logo
