On Sat, Nov 18, 2017 at 11:05:47PM +0100, Tomas Vondra wrote:
> Hi,
>
> On 11/18/2017 10:30 PM, David Fetter wrote:
> > On Sat, Nov 18, 2017 at 10:44:36AM -0500, Tom Lane wrote:
> >> jotpe writes:
> >>> I tried to enter invalid percentile fractions, and was astonished
> >>> that it seems to be ch
On 11/10/2017 02:32 PM, Martín Marqués wrote:
> Hi,
>
> Thanks for having a look at this patch.
>
> 2017-11-09 20:55 GMT-03:00 Jeff Janes :
>> On Fri, Sep 29, 2017 at 4:00 PM, Martin Marques
>> wrote:
>>>
>>> Hi,
>>>
>>> Some time ago I had to work on a system where I was cloning a standby
>>>
Hi,
On 09/13/2017 10:57 AM, Victor Drobny wrote:
> On 2017-09-09 06:03, Thomas Munro wrote:
>> Please send a rebased version of the patch for people to review and
>> test as that one has bit-rotted.
> Hello,
> Thank you for interest. In the attachment you can find rebased
> version(based on 69835b
On 15 November 2017 at 21:12, Thomas Rosenstein <
thomas.rosenst...@creamfinance.com> wrote:
> I would like somebody to consider Petr Jelineks patch for worker.c from
> here (https://www.postgresql.org/message-id/619c557d-93e6-1833-16
> 92-b010b176ff77%402ndquadrant.com)
>
> I'm was facing the sam
On Sun, Nov 19, 2017 at 12:56 AM, Peter Eisentraut
wrote:
> On 11/18/17 06:32, Michael Paquier wrote:
>> + cbind_header_len = 4 + strlen(state->channel_binding_type); /*
>> p=type,, */
>> + cbind_input_len = cbind_header_len + cbind_data_len;
>> + cbind_input = malloc(cbind_input
On Thu, Nov 16, 2017 at 2:16 PM, Jeff Janes wrote:
> e2c79e14 was to fix a pre-existing bug, but probably e9568083 made that bug
> easier to hit than it was before. (Which is not to say that e9568083 can't
> contain bugs of its own, of course)
I get that. I think that the same thing may have ha
Artur Zakirov writes:
> [ 0001-to-timestamp-format-checking-v7.patch ]
This patch needs a rebase over the formatting.c fixes that have gone
in over the last couple of days.
Looking at the rejects, I notice that in your changes to parse_format(),
you seem to be making it rely even more heavily on
On 11/18/2017 10:40 PM, Tom Lane wrote:
> Tomas Vondra writes:
>> while compiling on gcc 7.2.0 (on ARM), I got this warning:
>
>> rangetypes_spgist.c: In function 'spg_range_quad_inner_consistent':
>> rangetypes_spgist.c:559:29: warning: comparison between pointer and
>> zero charac
Hi,
On 11/18/2017 10:30 PM, David Fetter wrote:
> On Sat, Nov 18, 2017 at 10:44:36AM -0500, Tom Lane wrote:
>> jotpe writes:
>>> I tried to enter invalid percentile fractions, and was astonished
>>> that it seems to be checked after many work is done?
>>
>> IIRC, only the aggregate's final-functi
Tomas Vondra writes:
> On 11/02/2017 08:15 PM, Tom Lane wrote:
>> However, I'm not sure we're there yet, because there remains a fairly
>> nasty discrepancy even once we've gotten everyone onto the same page
>> about reltuples counting just live tuples: VACUUM and ANALYZE have
>> different definit
Hi,
On 11/02/2017 08:15 PM, Tom Lane wrote:
> Haribabu Kommi writes:
>> The changes are fine and now it reports proper live tuples in both
>> pg_class and stats. The other issue of continuous vacuum operation
>> leading to decrease of number of live tuples is not related to this
>> patch and that
Tomas Vondra writes:
> while compiling on gcc 7.2.0 (on ARM), I got this warning:
> rangetypes_spgist.c: In function 'spg_range_quad_inner_consistent':
> rangetypes_spgist.c:559:29: warning: comparison between pointer and
> zero character constant [-Wpointer-compare]
> if (i
Ildar Musin writes:
> [ ri_triggers_v2.patch ]
Pushed with two minor improvements. I noticed that ri_setdefault could
just go directly to ri_restrict rather than call the two separate triggers
that would end up there anyway; that lets its argument be "TriggerData
*trigdata" for more consistency
On Sat, Nov 18, 2017 at 10:44:36AM -0500, Tom Lane wrote:
> jotpe writes:
> > I tried to enter invalid percentile fractions, and was astonished
> > that it seems to be checked after many work is done?
>
> IIRC, only the aggregate's final-function is concerned with direct
> arguments, so it's not
Hi,
Apparently there was some minor breakage due to duplicate OIDs, so here
is the patch series updated to current master.
regards
--
Tomas Vondra http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
0001-Pass-all-keys-to-BRIN-consi
Hi,
Attached is an updated version of the patch, adopting the psql describe
changes introduced by 471d55859c11b.
regards
--
Tomas Vondra http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
0001-multivariate-MCV-lists.patch.gz
Descr
Hi,
while compiling on gcc 7.2.0 (on ARM), I got this warning:
rangetypes_spgist.c: In function 'spg_range_quad_inner_consistent':
rangetypes_spgist.c:559:29: warning: comparison between pointer and
zero character constant [-Wpointer-compare]
if (in->traversalValue != (Datum
On 11/18/17 12:05, Tom Lane wrote:
> Peter Eisentraut writes:
>> On 11/17/17 12:16, Tom Lane wrote:
>>> I'm confused by the places that change PLy_elog calls to pass NULL:
>>>
>>> - PLy_elog(ERROR, "could not create globals");
>>> + PLy_elog(ERROR, NULL);
>>>
>>> How is that an
Oliver Ford writes:
> Attached is v2 of src, tests and docs. Doc patch is unchanged from v1.
I took a quick look at this patch. The roman_to_int function itself seems
fairly reasonable, except that I don't like anything about the error
reporting. ERRCODE_INVALID_PARAMETER_VALUE doesn't really s
Peter Eisentraut writes:
> On 11/17/17 12:16, Tom Lane wrote:
>> I'm confused by the places that change PLy_elog calls to pass NULL:
>>
>> -PLy_elog(ERROR, "could not create globals");
>> +PLy_elog(ERROR, NULL);
>>
>> How is that an improvement? Otherwise it looks reason
On 18/11/17 16:50, Tom Lane wrote:
> Sophie Herold writes:
>> I need to test a (user) given column type name, with one in the database
>> for equality. To this end, I have to do some kind of normalization (e.g.
>> 'timestamptz(2)' to 'timestamp (2) with time zone'.)
>
> Perhaps format_type(oid, i
On 11/17/17 12:16, Tom Lane wrote:
> I'm confused by the places that change PLy_elog calls to pass NULL:
>
> - PLy_elog(ERROR, "could not create globals");
> + PLy_elog(ERROR, NULL);
>
> How is that an improvement? Otherwise it looks reasonable.
If we pass NULL, then the
On 11/18/17 06:32, Michael Paquier wrote:
> Here are some comments.
>
> +* The client requires channel biding. Channel binding type
> s/biding/binding/.
fixed
> if (!state->ssl_in_use)
> + /*
> +* Without SSL, we don't support ch
[cid:image001.png@01D3608D.8F5DC9E0]
Didier ROS
DSP/CSP IT-DMA/Solutions Groupe EDF/Expertise Applicative
Expertise SGBD
32 Avenue Pablo Picasso
92000 NANTERRE
Ce message et toutes les pièces jointes (ci-après le 'Message') sont établis à
l'intention exclusive des destinataires et les inform
Sophie Herold writes:
> I need to test a (user) given column type name, with one in the database
> for equality. To this end, I have to do some kind of normalization (e.g.
> 'timestamptz(2)' to 'timestamp (2) with time zone'.)
Perhaps format_type(oid, integer) would help you.
jotpe writes:
> I tried to enter invalid percentile fractions, and was astonished that
> it seems to be checked after many work is done?
IIRC, only the aggregate's final-function is concerned with direct
arguments, so it's not all that astonishing.
regards, tom lane
Hi,
I need to test a (user) given column type name, with one in the database
for equality. To this end, I have to do some kind of normalization (e.g.
'timestamptz(2)' to 'timestamp (2) with time zone'.)
Comparing the name alone is possible with to_regtype(type_name) or
::regtype. However, this ig
On Fri, Nov 10, 2017 at 8:39 PM, Robert Haas wrote:
> On Fri, Nov 10, 2017 at 5:44 AM, Amit Kapila wrote:
>> I am seeing the assertion failure as below on executing the above
>> mentioned Create statement:
>>
>> TRAP: FailedAssertion("!(!(tup->t_data->t_infomask & 0x0008))", File:
>> "heapam.c",
On Sat, Nov 18, 2017 at 2:57 AM, Fujii Masao wrote:
> On Fri, Nov 17, 2017 at 5:20 PM, Tsunakawa, Takayuki
> wrote:
>> From: Kyotaro HORIGUCHI [mailto:horiguchi.kyot...@lab.ntt.co.jp]
>>> The orinal code recycles some of the to-be-removed files, but the patch
>>> removes all the victims. This ma
On Thu, Nov 16, 2017 at 7:34 PM, Kyotaro HORIGUCHI
wrote:
> At Wed, 15 Nov 2017 16:13:01 +0900, Michael Paquier
> wrote in
>
>> pg_stat_get_mod_since_analyze(C.oid) AS n_mod_since_analyze,
>> + pg_stat_get_vacuum_necessity(C.oid) AS vacuum_required,
>> pg_st
On Sat, Nov 18, 2017 at 4:31 AM, Peter Eisentraut
wrote:
> I made some significant changes to the logic.
Thanks!
> The selection of the channel binding flag (n/y/p) in the client seemed
> wrong. Your code treated 'y' as an error, but I think that is a
> legitimate case, for example a PG11 clien
I tried to enter invalid percentile fractions, and was astonished that
it seems to be checked after many work is done?
psql (11devel)
Type "help" for help.
jotpe=# \timing
Timing is on.
jotpe=# select percentile_cont(array[0,0.25,0.5,1,1,null,2]) within
group(order by txk) from klima_tag;
ERR
32 matches
Mail list logo
