On Mon, Sep 19, 2016 at 11:20 AM, Mark Kirkwood
wrote:
>
>
> On 17/09/16 06:38, Andres Freund wrote:
>>
>> On 2016-09-16 09:12:22 -0700, Jeff Janes wrote:
>>>
>>> On Thu, Sep 15, 2016 at 7:23 AM, Andres Freund
>>> wrote:
One earlier question about this is whether that is actually a wort
Thanks a lot.
On Fri, Sep 16, 2016 at 7:07 PM, Tom Lane wrote:
> Ashutosh Bapat writes:
>>> I'd suggest that this is parallel to nodeToString() and therefore
>>> (a) should be placed beside it,
>
>> Done. Added it after nodeToString().
>
> Pushed, thanks.
>
> regards, tom
On Fri, Sep 16, 2016 at 6:00 PM, Rajkumar Raghuwanshi
wrote:
>
> On Fri, Sep 9, 2016 at 3:17 PM, Ashutosh Bapat
> wrote:
>>
>> Hi All,
>>
>> PFA the patch to support partition-wise joins for partitioned tables. The
>> patch
>> is based on the declarative parition support patches provided by Amit
You may want to add this to the November commitfest
https://commitfest.postgresql.org/11/.
On Fri, Sep 16, 2016 at 6:05 PM, Daniel Verite wrote:
> Hi,
>
> Following the discussion on forbidding an AUTOCOMMIT off->on
> switch mid-transaction [1], attached is a patch that let the hooks
> return a
On 17/09/16 06:38, Andres Freund wrote:
On 2016-09-16 09:12:22 -0700, Jeff Janes wrote:
On Thu, Sep 15, 2016 at 7:23 AM, Andres Freund wrote:
One earlier question about this is whether that is actually a worthwhile
goal. Are the speed and space benefits big enough in the general case?
Could
2016-09-16 10:31 GMT+02:00 Kyotaro HORIGUCHI <
horiguchi.kyot...@lab.ntt.co.jp>:
> Hello, this is the new version.
>
> At Tue, 13 Sep 2016 10:50:13 +0900 (Tokyo Standard Time), Kyotaro
> HORIGUCHI wrote in <
> 20160913.105013.65452566.horiguchi.kyot...@lab.ntt.co.jp>
> > > > This patch consists o
On Mon, Sep 19, 2016 at 2:41 AM, Tomas Vondra
wrote:
> But now that I look at the first post, I see it apparently used a plain
> tpc-b pgbench (with synchronous_commit=on) to show the benefits, which is
> the workload I'm running right now (results sometime tomorrow).
Good option, We can test pla
On Fri, Sep 09, 2016 at 09:57:21AM -0400, Peter Eisentraut wrote:
> Review of the patch in the commit fest:
>
> - Various naming/spelling inconsistencies: In the source, the module
> is require_where, the documentation titles it require-where, the GUC
> parameters are requires_where.*, but inc
Current PostgreSQL Documentation on recovery.conf has this about
recovery_min_apply_delay[1]:
---<---
This parameter is intended for use with streaming replication deployments;
however, if the parameter is specified it will be honored in all cases.
Synchronous replication is not affected by this
On 09/08/2016 06:59 PM, Petr Jelinek wrote:
Hi,
Updated version, this should address most of the things in Peter's
reviews so far, not all though as some of it needs more discussion.
Another bug report.
I had subscribed a subscriber database to a publication with 1 table
create table a (a
New patch in attach. 0001 and 0002 without changes.
0003 - patch contain improvements for pg_recvloginca, now pg_recvloginca
after receive SIGINT will send CopyDone package to postgresql and wait from
server CopyDone. For backward compatible after repeat send SIGINT
pg_recvloginca will continue im
On 09/18/2016 06:08 AM, Amit Kapila wrote:
On Sat, Sep 17, 2016 at 11:25 PM, Tomas Vondra
wrote:
On 09/17/2016 07:05 AM, Amit Kapila wrote:
On Sat, Sep 17, 2016 at 9:17 AM, Tomas Vondra
wrote:
On 09/14/2016 05:29 PM, Robert Haas wrote:
...
Sure, but you're testing at *really* high clie
On 09/08/2016 06:59 PM, Petr Jelinek wrote:
- the CREATE SUBSCRIPTION also tries to check if the specified
connection connects back to same db (although that check is somewhat
imperfect) and if it gets stuck on create slot it should be normally
cancelable (that should solve the issue Steve Sing
Hi
2016-09-16 10:31 GMT+02:00 Kyotaro HORIGUCHI <
horiguchi.kyot...@lab.ntt.co.jp>:
> Hello, this is the new version.
>
> At Tue, 13 Sep 2016 10:50:13 +0900 (Tokyo Standard Time), Kyotaro
> HORIGUCHI wrote in <
> 20160913.105013.65452566.horiguchi.kyot...@lab.ntt.co.jp>
> > > > This patch consis
On 10 August 2016 at 01:53, Pavel Stehule wrote:
> Hi
>
> 2016-08-03 13:54 GMT+02:00 Alexey Grishchenko :
>
>> On Wed, Aug 3, 2016 at 12:49 PM, Alexey Grishchenko <
>> agrishche...@pivotal.io> wrote:
>>
>>> Hi
>>>
>>> Current implementation of PL/Python does not allow the use of
>>> multi-dimensi
Pavel,
I will pick these up.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Wed, Sep 14, 2016 at 11:09 AM, Tatsuo Ishii wrote:
>> As I understand the issue, the main reason is that event triggers
>> execute procedures, and those exist in a single database only. If you
>> were to create an event trigger in database A, then a user gets created
>> in database B, your fun
Hello Amit,
[...]
Then you would get the -r cut at the end of the compound command. Thus the
current version gives full control of what will appear in the summary. If
I change "\into xxx\n" to mean "also cut here", then there is less control
on when the cut occurs when into is used.
So it mea
On 08/29/2016 09:10 AM, Haribabu Kommi wrote:
ecpg option --help alternative -? doesn't work in windows.
In windows, the PG provided getopt_long function is used
for reading the provided options.
The getopt_long function returns '?' for invalid characters
also but it sets optopt option to 0 in c
Hi
new update:
* doc is moved to better place - xml processing functions
* few more regress tests
* call forgotten check_srf_call_placement
Regards
Pavel
xmltable-8.patch.gz
Description: GNU Zip compressed data
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make ch
On Thu, Sep 15, 2016 at 10:07 PM, Robert Haas wrote:
> On Thu, Sep 15, 2016 at 4:53 AM, Amit Langote
> wrote:
>> Wow, this is bad. What is needed in this case is "canonicalization" of
>> the range partition bounds specified in the command.
>
> I think we shouldn't worry about this. It seems lik
21 matches
Mail list logo
