At 2015-04-10 20:00:35, "Michael Paquier" wrote:
>Interesting. I think that for the time being you should add it to the
>next commit fest to target an integration in 9.6 as these days we are
>busy wrapping up the last commit fest of 9.5:
>https://commitfest.postgresql.org/5/
I had add it to th
On Tue, Apr 7, 2015 at 10:57 PM, Fabrízio de Royes Mello <
fabriziome...@gmail.com> wrote:
>
>
> On Tue, Apr 7, 2015 at 10:15 PM, Alvaro Herrera
wrote:
> >
> > Fabrízio de Royes Mello wrote:
> > > On Mon, Apr 6, 2015 at 12:53 AM, Alvaro Herrera <
alvhe...@2ndquadrant.com>
> > > wrote:
> > > >
> >
Hi
I wrote a prototype of this patch, and it works well
postgres=# set client_encoding to 'latin2';
SET
Time: 1.488 ms
postgres=# \copy (select xmlelement(name xx, d) from d) to ~/d.xml (format
'raw')
COPY 1
Time: 1.108 ms
postgres=# copy (select xmlelement(name xx, d) from d) to stdout (format
'
On 10/04/15 22:16, Tomas Vondra wrote:
On 04/10/15 21:57, Petr Jelinek wrote:
On 10/04/15 21:26, Peter Eisentraut wrote:
But this was not really my point, the BERNOULLI just does not work
well with row-limit by definition, it applies probability on each
individual row and while you can get pr
On 04/10/15 21:57, Petr Jelinek wrote:
On 10/04/15 21:26, Peter Eisentraut wrote:
But this was not really my point, the BERNOULLI just does not work
well with row-limit by definition, it applies probability on each
individual row and while you can get probability from percentage very
easily (j
On 10/04/15 21:26, Peter Eisentraut wrote:
On 4/9/15 8:58 PM, Petr Jelinek wrote:
Well, you can have two approaches to this, either allow some specific
set of keywords that can be used to specify limit, or you let sampling
methods interpret parameters, I believe the latter is more flexible.
Ther