t sum(xact_commit + xact_rollback)
from pg_stat_database
[2] Message from the log, saying what is obvious
LOG: 0: using stale statistics instead of current ones because
stats collector is not responding
--
Jaime Casanova
Director de Servicios Profesionales
SystemGuards - Consultores de PostgreSQL
< 0.2 then null else random() * 1000 end,
random() * 1
from generate_series(1, 100) seq
on conflict (nullable_int) do nothing;
for master I just dumped the data from the table and loaded it. I'm also
attaching the queries I used.
After this tests, I'm not conv
>
> > Thoughts?
> >
> > James
> >
> > 1: https://commitfest.postgresql.org/30/2754/
> >
> >
> Oops...
> I must have rushed with this one, thank you for noticing.
> I don't see how to move it back either. I think it's fine to mark it as
> Committed where it is now.
>
BTW, I still see this one as needs review
--
Jaime Casanova
Professional PostgreSQL: Soporte 24x7 y capacitación
e_table()
RETURNS void
LANGUAGE sql
BEGIN ATOMIC
CREATE TABLE created_table AS SELECT * FROM int8_tbl;
END;
ERROR: unrecognized token: "?"
CONTEXT: SQL function "make_table"
"""
Attached a backtrace from the point the error is thrown.
--
Jaime Casanova
D
ently the END in the CASE expression is interpreted as the END of
the function
--
Jaime Casanova
Director de Servicios Profesionales
SYSTEMGUARDS - Consultores de PostgreSQL
_type where exists (select 1 from pg_authid fetch
first 10 percent rows only);
"""
postgres was compiled with these options:
"""
CFLAGS="-ggdb -O0 -g3 -fno-omit-frame-pointer" ./configure
--prefix=/opt/var/pgdg/14dev/percent --enable-debug --enable-cassert
--
else I can do to help with this
one.
--
Jaime Casanova
Director de Servicios Profesionales
SystemGuards - Consultores de PostgreSQL
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
set = {__val = {0, 140734235450160, 2, 6, 6456150, 94891112648656,
4611686018427388799
On Wed, Jan 27, 2021 at 2:09 AM Peter Geoghegan wrote:
>
> On Tue, Jan 26, 2021 at 10:52 PM Jaime Casanova
> wrote:
> > ${subject} happened while executing ${attached query} at regresssion
> > database, using 14dev (commit
> > d5a83d79c9f9b660a6a5a77afafe146d3c8c6f
Hi,
Attached is a small patch for ${subject}
--
Jaime Casanova
Director de Servicios Profesionales
SystemGuards - Consultores de PostgreSQL
diff --git a/contrib/pg_stat_statements/pg_stat_statements.c b/contrib/pg_stat_statements/pg_stat_statements.c
index 72a117fc19..62cccbfa44 100644
--- a
Hi,
Just found another crash.
Seems that commit a929e17e5a8c9b751b66002c8a89fdebdacfe194 broke something.
Attached is a minimal case and the stack trace.
--
Jaime Casanova
Director de Servicios Profesionales
SystemGuards - Consultores de PostgreSQL
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps
On Thu, Jan 28, 2021 at 9:45 PM Jaime Casanova
wrote:
>
> Hi,
>
> Just found another crash.
>
> Seems that commit a929e17e5a8c9b751b66002c8a89fdebdacfe194 broke something.
> Attached is a minimal case and the stack trace.
>
Hi,
Seems this is the same that A
Hi,
Second paragraph of this comment (procarray.c:1604) says:
* See the definition of ComputedXidHorizonsResult for the various computed
It should say ComputeXidHorizonsResult (it has an extra "d" in Computed)
--
Jaime Casanova
Director de Servicios Profesionales
SystemGuards - Cons
on the same
thread causes http://cfbot.cputube.org/ to fail.
Now; I do think that the secondd patch, the one that just skips update
of the state in control file, is the way to go. The other patch adds too
much complexity for a small return.
--
Jaime Casanova
Director de Servicios Profesionales
SystemGuards - Consultores de PostgreSQL
On Wed, Nov 17, 2021 at 08:04:41PM +, Jacob Champion wrote:
> On Wed, 2021-11-17 at 14:44 -0500, Jaime Casanova wrote:
> > I'm trying to add more parallelism by copying individual segments
> > of a relfilenode in different processes. Does anyone one see a big
> > pr
races.
FWIW, the second crash doesn't appear to be caused by the MERGE patch
but I cannot trigger it other way.
--
Jaime Casanova
Director de Servicios Profesionales
SystemGuards - Consultores de PostgreSQL
merge1.sql
Description: application/sql
#0 __GI_raise (sig=sig@entry=
kend/utils/adt/ruleutils.c:3292, but instead it has an assert
that gets hit with something like this:
CREATE FUNCTION foo() RETURNS int LANGUAGE SQL AS $$ SELECT 1 $$;
SELECT pg_get_function_sqlbody('foo'::regproc);
--
Jaime Casanova
Director de Servicios Profesionales
SYSTEMGUARDS - Consultores de PostgreSQL
"""
create table t1 (col1 text, col2 text);
create unique index on t1 ((col1 || col2));
insert into t1 values((select array_agg(md5(g::text))::text from
generate_series(1, 256) g), version());
"""
Attached is a backtrace from current HEAD
--
Jaime Casanova
D
g() line 6 at OPEN
--
Jaime Casanova
Director de Servicios Profesionales
SYSTEMGUARDS - Consultores de PostgreSQL
On Wed, Mar 31, 2021 at 7:50 AM Ashutosh Bapat
wrote:
>
> On Wed, Mar 31, 2021 at 6:09 AM Jaime Casanova
>
> >
> > -- this fails
> > update t2 set i = 5 returning cursor_bug() as c1;
> > ERROR: cursor "c1" already in use
> > CONTEXT: PL/pgSQL fu
'2021-01-01'::timestamp
with time zone, '2021-01-31', '5 days') tz limit 1)
;
```
attached a backtrace. Let me know if you need extra information.
--
Jaime Casanova
Director de Servicios Profesionales
SYSTEMGUARDS - Consultores de PostgreSQL
#0 __GI_raise (sig=s
ge the ranges a bit differently).
>
>
I can confirm this fixes the crash in the query I showed and the original case.
--
Jaime Casanova
Director de Servicios Profesionales
SYSTEMGUARDS - Consultores de PostgreSQL
On Wed, Mar 31, 2021 at 6:19 PM Jaime Casanova
wrote:
>
> On Wed, Mar 31, 2021 at 5:25 PM Tomas Vondra
> wrote:
> >
> > Hi,
> >
> > I think I found the issue - it's kinda obvious, really. We need to
> > consider the timezone, because the "tim
gbench:
pgbench -i postgres
psql -c "CREATE INDEX ON pgbench_history USING brin (tid
int4_minmax_multi_ops);" postgres
pgbench -c2 -j2 -T 300 -n postgres
Attached a backtrace
--
Jaime Casanova
Director de Servicios Profesionales
SystemGuards - Consultores de PostgreSQL
#0 __GI_ra
little patch for that.
Should I add an entry for this on next commitfest?
--
Jaime Casanova
Director de Servicios Profesionales
SystemGuards - Consultores de PostgreSQL
diff --git a/src/backend/access/gin/ginfast.c b/src/backend/access/gin/ginfast.c
index e0d9940946..305326119c 100644
--- a/src
On Mon, Apr 05, 2021 at 10:41:22AM -0300, Euler Taveira wrote:
> On Mon, Apr 5, 2021, at 3:31 AM, Jaime Casanova wrote:
> > When AV worker items where introduced 4 years ago, i was suggested that
> > it could be used for other things like cleaning the pending list of GIN
> >
clear that is disabled by default (at least the way it
was written made no sense for me, but it could be that my english is
not that good).
--
Jaime Casanova
Director de Servicios Profesionales
SystemGuards - Consultores de PostgreSQL
diff --git a/doc/src/sgml/brin.sgml b/doc/src/sgml/brin.sgml
oom_ops, j int4_bloom_ops )
with (pages_per_range=116);
so, for having:
two int columns - PAGES_PER_RANGE should be max 116
three int columns - PAGES_PER_RANGE should be max 77
one int and one timestamp - PAGES_PER_RANGE should be max 121
and so on
--
Jaime Casanova
Director de
On Thu, Apr 08, 2021 at 12:18:36PM +0200, Tomas Vondra wrote:
> On 4/8/21 9:08 AM, Jaime Casanova wrote:
> > Hi everyone,
> >
> > When testing brin bloom indexes I noted that we need to reduce the
> > PAGES_PER_RANGE parameter of the index to allow more columns on it.
t; The current version is ICU 67.
>
Hi,
Sadly, that is managed by EDB and not by the community.
You can try
https://www.2ndquadrant.com/en/resources/postgresql-installer-2ndquadrant/
which uses ICU-62.2, is not the latest but should allow you to follow
the examples in the documentation.
--
Jaime
On Tue, 11 Aug 2020 at 13:45, Thomas Kellerer wrote:
>
> Jaime Casanova schrieb am 11.08.2020 um 20:39:
> >> As a follow-up to bug #16570 [1] and other previous discussions
> >> on the mailing-lists, I'm checking out PG13 beta for Windows
> >> from:
> >
d understand if
you decide is not a first patch material.
Anyway, a +1 to your proposal.
--
Jaime Casanova
Director de Servicios Profesionales
SystemGuards - Consultores de PostgreSQL
Ok, subject was a bit philosophical but this message I just found is
quite confusing.
"""
regression=# select cast(null as anyrange) &> cast(null as anymultirange);
ERROR: argument declared anymultirange is not a multirange type but type
anymultirange
""&
'm asking because no one did it before,
that could not be a good sign.
--
Jaime Casanova
Director de Servicios Profesionales
SystemGuards - Consultores de PostgreSQL
diff --git a/doc/src/sgml/ref/pgupgrade.sgml b/doc/src/sgml/ref/pgupgrade.sgml
index 20efdd7..74eaaee 100644
--- a/doc/src/sgml/r
art_0 partition of t1_part for values with (modulus
2, remainder 0);
create table t1_part_1 partition of t1_part for values with (modulus
2, remainder 1);
insert into t1_part values (1, repeat('abcdefquerty', 20));
create index on t1_part (i) include (t);
--
Jaime Casanova
cture as suggested by Amit.
>
> But it will be better to have a ATTACH PARTITION test too.
>
the patch worked for me, i also tried some combinations using ATTACH
PARTITION and found no problems
--
Jaime Casanova www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
a pg9.1 in a pg11. It was very useful to find queries that
are affected but changes in default values of GUCs.
Normally, a query that works in an old version will work in a new one; but
this is useful to catch the few that don't if any
--
Jaime Casanova www.2ndQuadrant.co
ke advantage of new plans for example if i'm
migrating from 9.5 to 9.6+ i would prefer that, when replaying, the queries
use parallel plans so i quickly get if that would somehow be a problem (for
example by using more cpu than before)
--
Jaime Casanova www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
may be used uninitialized in
this function [-Wmaybe-uninitialized]
lts->nBlocksAllocated = lt->offsetBlockNumber + tapeblocks;
~~^~~~
"""
Can we please, initialize tapeblocks variable in
ltsConcatWorkerTapes() function
On 13 February 2018 at 21:07, Jaime Casanova
wrote:
> Hi,
>
> Compiling with CFLAGS="-ggdb -Og -g3 -fno-omit-frame-pointer" as
> recommended in https://wiki.postgresql.org/wiki/Developer_FAQ#Compile-time
>
> My compiler gives me this message
>
> ""&quo
On 13 February 2018 at 23:10, Tom Lane wrote:
> Jaime Casanova writes:
>>> My compiler gives me this message
>>> logtape.c: In function ‘ltsConcatWorkerTapes’:
>>> logtape.c:462:48: warning: ‘tapeblocks’ may be used uninitialized in
>>> this f
t for this slot?
do you see a process in pg_stat_activity for that pid? in the os?
--
Jaime Casanova www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
i);
alter table t1 add primary key using index t1_i_idx ;
"""
the ALTER TABLE ADD PK does not recurse to partitions, which maybe is
perfectly fine because i'm using USING INDEX but it feels like an
oversight to me
--
Jaime Casanova www.2ndQuadrant.co
On Mon, Mar 21, 2022 at 05:34:31PM -0700, Andres Freund wrote:
> Hi,
>
> On 2022-02-01 21:57:00 -0500, Jaime Casanova wrote:
> > This patch adds a new option (-J num, --jobs-per-disk=num) in
> > pg_upgrade to speed up copy mode. This generates upto ${num}
> > proce
on_table_level2 as ref_0;
"""
Attached the backtrace.
PS: I'm cc'ing Andrew and Nikita because my feeling is that this is
f4fb45d15c59d7add2e1b81a9d477d0119a9691a responsability.
--
Jaime Casanova
Director de Servicios Profesionales
SystemGuards - Consultores
as regoperator)) as cstring),
cast((select pronamespace from pg_catalog.pg_proc limit 1 offset 1)
as oid),
cast(subq_1.pid as int4)) as c0
from pg_catalog.pg_stat_progress_analyze as subq_1
"""
--
Jaime Casanova www.2ndQuadrant.com
PostgreSQL Dev
ll it gives an error because the file doesn't
exists) but crash the server on 12+
attached the stack trace from master
--
Jaime Casanova www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
#0 0x00a3a3f1 in table_beginscan_
ginal thread:
https://www.postgresql.org/message-id/flat/YZVbtHKYP02AZDIO%40ahch-to
--
Jaime Casanova
Director de Servicios Profesionales
SystemGuards - Consultores de PostgreSQL
>From 0d04f79cb51d6be0ced9c6561cfca5bfe18c4bdd Mon Sep 17 00:00:00 2001
From: Jaime Casanova
Date: Wed, 15 Dec 2021
here was some kind of guide about
this, and of course the wiki has that guide (outdated yes but something
to start with).
https://wiki.postgresql.org/wiki/CommitFest_Checklist#Sudden_Death_Overtime
This needs some love, still mentions rrreviewers for example, but if we
updated and put here a clear de
On Wed, Feb 02, 2022 at 01:00:18PM -0500, Tom Lane wrote:
>
> Anyway, thanks to Julien for doing this mostly-thankless task
> this time!
>
Agreed, great work!
--
Jaime Casanova
Director de Servicios Profesionales
SystemGuards - Consultores de PostgreSQL
On Sat, May 15, 2021 at 08:12:51AM +0200, Joel Jacobson wrote:
> On Mon, Apr 5, 2021, at 16:47, Jaime Casanova wrote:
> > On Mon, Apr 05, 2021 at 10:41:22AM -0300, Euler Taveira wrote:
> > > On Mon, Apr 5, 2021, at 3:31 AM, Jaime Casanova wrote:
> > > > When AV w
On Sun, Apr 04, 2021 at 07:52:50PM +0200, Tomas Vondra wrote:
> On 4/4/21 7:25 AM, Jaime Casanova wrote:
> >
> > pgbench -i postgres
> > psql -c "CREATE INDEX ON pgbench_history USING brin (tid
> > int4_minmax_multi_ops);" postgres
> > pgbench -c2
On Mon, Oct 03, 2022 at 07:53:34PM +0200, Tomas Vondra wrote:
> On 9/29/22 08:53, Jaime Casanova wrote:
> > ...
> >
> > Just found one more ocurrance of this one with this index while an
> > autovacuum was running:
> >
> > """
> > CRE
On Mon, Oct 03, 2022 at 10:29:38PM +0200, Tomas Vondra wrote:
> On 10/3/22 21:25, Jaime Casanova wrote:
> > On Mon, Oct 03, 2022 at 07:53:34PM +0200, Tomas Vondra wrote:
> >> On 9/29/22 08:53, Jaime Casanova wrote:
> >>> ...
> >>>
> >>> Jus
ss and few bugs.
>
Congrats Daniel and John. Keep your good work!
--
Jaime Casanova
Director de Servicios Profesionales
SystemGuards - Consultores de PostgreSQL
regclass, bigint) function,
> - which is useful when the index tuple is no longer a very good
> - representation because the existing values have changed.
> +
> +
I feel that somewhere in this paragraph it should be mentioned that is
off by default.
otherwise, +1
--
Jaime Casanova
Director de Servicios Profesionales
SystemGuards - Consultores de PostgreSQL
Hi everyone,
Do we already have a ${subject}? Otherwise I could offer my self.
If anyone agree, this would be my first time as CFM as I would
appreciate some help.
--
Jaime Casanova
Director de Servicios Profesionales
SystemGuards - Consultores de PostgreSQL
On Wed, Sep 01, 2021 at 03:10:32PM +0200, Daniel Gustafsson wrote:
> It is now 2021-09-01 Anywhere On Earth so I’ve set the September commitfest to
> In Progress and opened the November one for new entries. Jaime Casanova has
> volunteered for CFM [0], so let’s help him close the 284 s
Hi,
This doesn't pass tests because of lack of some file. Can we fix that
please and send the patch again?
On Tue, Aug 10, 2021 at 7:20 AM Simon Riggs
wrote:
> On Wed, 14 Jul 2021 at 12:48, vignesh C wrote:
>
> > The patch does not apply on Head anymore, could you rebase and post a
> > patch.
On Wed, Sep 01, 2021 at 06:32:38PM +0200, Magnus Hagander wrote:
> On Wed, Sep 1, 2021 at 4:26 PM Jaime Casanova
> wrote:
> >
> > On Wed, Sep 01, 2021 at 03:10:32PM +0200, Daniel Gustafsson wrote:
> > > It is now 2021-09-01 Anywhere On Earth so I’ve set the September
&
obody else using that compiler out in
> > the real world, but we don't know that.
> >
>
> OK. Will do.
>
Hi Dean,
It seems you already committed this. But it's still as "Ready for
committer" in the commitfest app.
Are we waiting for something else or we can mark it as committed?
--
Jaime Casanova
Director de Servicios Profesionales
SystemGuards - Consultores de PostgreSQL
1] https://github.com/anarazel/postgres/tree/shmstat
> [2]
> https://www.postgresql.org/message-id/20210722205458.f2bug3z6qzxzpx2s%40alap3.anarazel.de
>
>
Hi Andres,
Are you going planning to post a rebase soon?
--
Jaime Casanova
Director de Servicios Profesionales
SystemGuards - Consultores de PostgreSQL
Hi Paul,
Thanks for working on this. It would be a great improvement.
I wanted to test the patches but:
patch 01: does apply but doesn't compile, attached the compile errors.
patch 04: does not apply clean.
Please fix and resend.
--
Jaime Casanova
Director de Servicios Profesionales
Sy
On Mon, May 17, 2021 at 01:46:37PM +0900, Masahiko Sawada wrote:
> On Mon, Apr 5, 2021 at 3:31 PM Jaime Casanova
> wrote:
> >
> > Hi,
> >
> > When AV worker items where introduced 4 years ago, i was suggested that
> > it could be used for other things l
.patch extension
instead of .txt, that way the CI at http://commitfest.cputube.org/ will
be able to execute automatic tests on it.
Regards,
--
Jaime Casanova
Director de Servicios Profesionales
SystemGuards - Consultores de PostgreSQL
Álvaro,
Are we waiting for another version of the patch based on Andres'
comments? Or this version is good enough for testing?
BTW, current patch still applies cleanly.
regards,
--
Jaime Casanova
Director de Servicios Profesionales
SystemGuards - Consultores de PostgreSQL
et.c:126
126 if (shorter->words[i] != longer->words[i])
"""
attached are the query that triggers the crash and the backtrace.
--
Jaime Casanova
Director de Servicios Profesionales
SystemGuards - Consultores de PostgreSQL
bug.sql
Description: application/s
ion...
>
Since there is no clear definition here, we seems to be expecting an
example of how the hook will be used and there have been no activity
since may.
I suggest we move this to Returned with feedback. Which I'll do in a
couple hours.
--
Jaime Casanova
Director de Servicios Profesionales
SystemGuards - Consultores de PostgreSQL
The patch does not apply on Head anymore, could you rebase and post a
> > > patch. I'm changing the status to "Waiting for Author".
> >
> > Okay, I will rebase and send it by next week.
>
> I have rebased the patch.
>
Hi,
This doesn't apply clean
On Fri, Sep 10, 2021 at 10:54:04AM +0530, Dilip Kumar wrote:
> On Fri, 10 Sep 2021 at 10:40 AM, Jaime Casanova <
> jcasa...@systemguards.com.ec> wrote:
>
> > On Mon, Jul 19, 2021 at 01:24:03PM +0530, Dilip Kumar wrote:
> > > On Sun, Jul 18, 2021 at
On Thu, Sep 02, 2021 at 07:27:09AM +0100, Dean Rasheed wrote:
> On Thu, 2 Sept 2021 at 00:39, Jaime Casanova
> wrote:
> >
> > Hi Dean,
> >
> > It seems you already committed this. But it's still as "Ready for
> > committer" in the commitfest a
I've rebased the patch against current master to take it to v15.
>
> I've then worked on the patch some myself to make v16 (attached),
> adding these things:
>
Hi Simon,
This one doesn't apply nor compile anymore.
Can we expect a rebase soon?
--
Jaime Casanova
On Mon, Sep 06, 2021 at 12:52:37PM -0700, Paul A Jungwirth wrote:
> On Sat, Sep 4, 2021 at 12:56 PM Jaime Casanova
> wrote:
> >
> > patch 01: does apply but doesn't compile, attached the compile errors.
> > patch 04: does not apply clean.
>
> Thanks for ta
On Wed, Sep 01, 2021 at 09:26:33AM -0500, Jaime Casanova wrote:
> On Wed, Sep 01, 2021 at 03:10:32PM +0200, Daniel Gustafsson wrote:
> > It is now 2021-09-01 Anywhere On Earth so I’ve set the September commitfest
> > to
> > In Progress and opened the November one for new ent
pply on Head anymore, could you rebase and post a
> > patch. I'm changing the status to "Waiting for Author".
>
> Here's a rebased version. I also squashed that little bug fix from previous
> patch set.
>
Hi,
This patch does not apply, can you submit a rebased version?
--
Jaime Casanova
Director de Servicios Profesionales
SystemGuards - Consultores de PostgreSQL
Hi,
BTW, this only happens when the third parameter is large. Here is an
example that consistently crash here:
select regexp_count('jaime.casanova', 'valid', 102481);
--
Jaime Casanova
Director de Servicios Profesionales
SystemGuards - Consultores de PostgreSQL
quot;
regression=# create temp variable random_number numeric on commit drop;
CREATE VARIABLE
regression=# \dV
Did not find any schema variables.
regression=# declare q cursor for select 1;
ERROR: DECLARE CURSOR can only be used in transaction blocks
"""
About that, why are you not usi
uffer page cannot be indexed.
Consider a function index of an MD5 hash of the value, or use full text
indexing.
"""
So, what is it? the index row size could be upto 8191 or cannot be
greater than 2704?
regards,
--
Jaime Casanova
Director de Servicios Profesionales
SystemGuards - Consultores de PostgreSQL
has been created before. A TEMP variable with an
ON COMMIT DROP created outside an explicit transaction will disappear
immediatly like cursor does in the same situation.
--
Jaime Casanova
Director de Servicios Profesionales
SystemGuards - Consultores de PostgreSQL
Hi Tomas,
Just noted that this query crash the server. Execute it in the
regression database:
"""
update brintest_multi set inetcol = '192.168.204.50/0'::inet;
"""
Attached is the backtrace. Let me know if you need something else to
track it.
On Sun, Sep 12, 2021 at 08:23:44PM -0500, Justin Pryzby wrote:
> On Sun, Sep 12, 2021 at 07:44:47PM -0500, Jaime Casanova wrote:
> > Hi Tomas,
> >
> > Just noted that this query crash the server. Execute it in the
> > regression database:
>
> If I'm
On Sat, Sep 11, 2021 at 01:35:27AM -0500, Jaime Casanova wrote:
> On Wed, Jul 14, 2021 at 06:04:14PM +0300, Heikki Linnakangas wrote:
> > On 14/07/2021 15:12, vignesh C wrote:
> > > On Sat, Jan 23, 2021 at 3:49 AM Heikki Linnakangas
> > > wrote:
> > > > H
as cidr) = c)
where subq_0.c9 <= subq_0.c24
"""
Attached the backtrace.
--
Jaime Casanova
Director de Servicios Profesionales
SystemGuards - Consultores de PostgreSQL
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
set = {__val = {4
ted
> > > > version of my "phase diagram" finger painting, to show how it looks
> > > > with these three patches. "scan*" is new.
> > >
0002: my only concern is that this will cause innecesary pain in
backpatch-ing future code... but not doing that myself will let that to
the experts
0003: i'm testing this now, not at a big scale but just to try to find
problems
--
Jaime Casanova
Director de Servicios Profesionales
SystemGuards - Consultores de PostgreSQL
arked as "Ready for committer" but it doesn't apply anymore.
--
Jaime Casanova
Director de Servicios Profesionales
SystemGuards - Consultores de PostgreSQL
e it's SQL exposed.
> > So maybe we should use your LockOid patch now, and refactor in the future
> > if we
> > add additional work-item types.
>
> Thoughts on this, Álvaro? I can see that the first version of this patch was
> not ideal but the rework seems to have
reviewing the other patches in regards to the NOT
> NULL tracking and maybe come back to this once the dust has settled
> and everyone is clear on how we determine if a column is NULL or not.
>
> Let me know your thoughts.
>
Hi Surafel,
We haven't seen an answer from yo
ication)
I wonder why validate_publication is passed as an argument just to
return if it's false, why not just test it before calling those
functions? Maybe is just a matter of style.
+get_publications_str(List *publications, StringInfo dest, bool quote_literal)
what's the purpose of the quote_literal argument?
--
Jaime Casanova
Director de Servicios Profesionales
SystemGuards - Consultores de PostgreSQL
h?
>
> [Added Andrew to recipients]
>
> Andrew, would you care to comment?
>
Hi everyone,
This is still marked as needs review, but I think it should be marked
as "Returned with feedback" or "waiting on author".
suggestions?
--
Jaime Casanova
Director de Servicios Profesionales
SystemGuards - Consultores de PostgreSQL
only
) as subq_0
where case when (subq_0.c5 < 2)
then cast(null as jsonb)
else cast(null as jsonb)
end ? ref_0.c
"""
And because it needs pagg_tab_ml it should be run a regression database.
This affects at least 14 and 15.
Attached is the backtr
ill on "Needs review"!
Should we change it to Committed or is expected something else
about it?
--
Jaime Casanova
Director de Servicios Profesionales
SystemGuards - Consultores de PostgreSQL
the
> > scales .. so that they each have more digits ..." which seems clear
> > enough; I think the new comment is a bit on the short side.
> >
>
> OK, that's a fair point. Updated version attached.
>
Hi Dean,
Are you planning to commit this soon?
--
gt; on this approach? I fear that it will be the west of effort if
> Andrew comes up with the patch for his approach.
> Andrew Gierth: Are you working on your approach?
>
Hi Surafel,
I'm marking this one as "returned with feedback". Then you or Andrew can
submit a new versio
On Sat, Sep 11, 2021 at 12:52:10AM -0500, Jaime Casanova wrote:
> On Wed, Sep 01, 2021 at 09:26:33AM -0500, Jaime Casanova wrote:
> > On Wed, Sep 01, 2021 at 03:10:32PM +0200, Daniel Gustafsson wrote:
> > > It is now 2021-09-01 Anywhere On Earth so I’ve set the September
&
ovement in latency and/or throughput. Something like that.
> Doesn't have to be a huge improvement.
>
Hi Simon,
This has been stalled since July, and based on Peter's comment i feel we
should mark this as RwF. Which i'm doing now.
Please feel free to resubmit for Next Commitfest.
--
Jaime Casanova
Director de Servicios Profesionales
SystemGuards - Consultores de PostgreSQL
On Fri, Oct 01, 2021 at 07:56:33AM +0100, Dean Rasheed wrote:
> On Thu, 30 Sept 2021 at 18:25, Jaime Casanova
> wrote:
> >
> > Are you planning to commit this soon?
> >
>
> Yes, I'll take a look at it next week.
>
Hi Dean,
Great! I'll move the CF ent
On Thu, Sep 02, 2021 at 10:20:50AM -0500, Jaime Casanova wrote:
> On Mon, Jul 26, 2021 at 06:27:54PM -0700, Andres Freund wrote:
> > Hi,
> >
> > On 2021-07-26 17:52:01 +0900, Kyotaro Horiguchi wrote:
> > > > > Yeah, thank you very much for checking that.
aving it here unless someone else needs to pick
> it up for their extension work. The in-principle agreement is there for
> future work anyway.
Hi Craig,
There is still a CF entry for this. Should we close it as withdrawn? or
maybe RwF?
--
Jaime Casanova
Director de Servicios Profesionales
SystemGuards - Consultores de PostgreSQL
On Fri, Oct 01, 2021 at 08:53:23AM -0500, Jaime Casanova wrote:
>
> Anyway we need to advance to a close, so I need help with:
>
> - what should we do with WoA patches? moving them to the Next CF?
Correcting myself, we cannot move WoA patches. So we should just close
them with R
On Fri, Oct 01, 2021 at 01:34:45PM -0400, Tom Lane wrote:
> Jaime Casanova writes:
> > Correcting myself, we cannot move WoA patches. So we should just close
> > them with RwF.
>
> Uh, really? I don't think that's been common practice in the past.
> I thought w
On Fri, Oct 01, 2021 at 01:43:23PM -0400, Andrew Dunstan wrote:
>
> On 10/1/21 1:31 PM, Jaime Casanova wrote:
> > On Fri, Oct 01, 2021 at 08:53:23AM -0500, Jaime Casanova wrote:
> >> Anyway we need to advance to a close, so I need help with:
> >>
> >> - wha
1 - 100 of 154 matches
Mail list logo
