ss and few reverts!
>
No surprise here! Congratulations to both of you!
You both have done a great job!
--
Jaime Casanova
SYSTEMGUARDS S.A.
Hi,
The attached query makes beta2 crash with attached backtrace.
Interestingly the index on ref_6 is needed to make it crash, without
it the query works fine.
--
Jaime Casanova
Director de Servicios Profesionales
SYSTEMGUARDS - Consultores de PostgreSQL
#0 __GI_raise (sig=sig@entry=6
: VACUUM
public.array_index_op_test
--
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 = {4194304, 140730796945184, 2, 6, 7058320,
94276041338800, 4611686018427388799
On Thu, Jun 8, 2023 at 7:22 PM Joe Conway wrote:
>
> On 6/8/23 20:02, Jaime Casanova wrote:
> > Hi,
> >
> > Someone made https://git.postgresql.org/ depressed
> >
> > After not being able to pull, I dropped and tried to clone again:
>
>
> Try now
&g
tgresql.org/git/postgresql.git/': Empty reply from
server
"""
--
Jaime Casanova
Director de Servicios Profesionales
SYSTEMGUARDS - Consultores de PostgreSQL
>
ok, this doesn't deserve that much attention anyway...
It doesn't seem to do any harm, so I'm not spending more time on it
--
Jaime Casanova
Director de Servicios Profesionales
SYSTEMGUARDS - Consultores de PostgreSQL
On Wed, Jun 7, 2023 at 5:19 AM Drouvot, Bertrand
wrote:
>
> Hi,
>
> On 6/7/23 7:32 AM, Jaime Casanova wrote:
> >
> > So, I wonder if that function is really needed because as I said I
> > solved it with already existing functionality. Or if it is reall
existing functionality. Or if it is really
needed maybe it is a bug that a CHECKPOINT and pg_switch_wal() have
the same effect?
--
Jaime Casanova
Director de Servicios Profesionales
SYSTEMGUARDS - Consultores de PostgreSQL
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
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 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
On Fri, Sep 16, 2022 at 02:37:17PM +0900, Kyotaro Horiguchi wrote:
> At Thu, 15 Sep 2022 11:15:12 -0500, Jaime Casanova
> wrote in
> > It fails at ./src/backend/utils/activity/pgstat_shmem.c:530 inside
>
> Thanks for the info. I reproduced by make check.. stupid..
>
&g
On Thu, Sep 15, 2022 at 05:30:11PM +0900, Kyotaro Horiguchi wrote:
> At Thu, 15 Sep 2022 01:26:15 -0500, Jaime Casanova
> wrote in
> > On Tue, Sep 13, 2022 at 10:07:50PM -0500, Jaime Casanova wrote:
> > > On Tue, Sep 13, 2022 at 06:48:45PM +0900, Ky
On Tue, Sep 13, 2022 at 10:07:50PM -0500, Jaime Casanova wrote:
> On Tue, Sep 13, 2022 at 06:48:45PM +0900, Kyotaro Horiguchi wrote:
> >
> > Another measure would be to add the region to wipe-out on reset to
> > PgStat_KindInfo, but it seems too much.. (attached)
> &
On Tue, Sep 13, 2022 at 06:48:45PM +0900, Kyotaro Horiguchi wrote:
> Nice finding.
>
> At Tue, 13 Sep 2022 00:39:45 -0500, Jaime Casanova
> wrote in
> > and the problem seems to be that after zero'ing the stats that includes
> > the name of the replication slot,
On Wed, Sep 07, 2022 at 12:39:08PM -0700, Andres Freund wrote:
> Hi,
>
> On 2022-09-06 18:40:49 -0500, Jaime Casanova wrote:
> > I'm not sure what is causing this, but I have seen this twice. The
> > second time without activity after changing the set of tables in a
> &g
On Wed, Sep 07, 2022 at 12:39:08PM -0700, Andres Freund wrote:
> Hi,
>
> On 2022-09-06 18:40:49 -0500, Jaime Casanova wrote:
> > I'm not sure what is causing this, but I have seen this twice. The
> > second time without activity after changing the set of tables in a
> >
n '3',
publication_names '"pub_pgbench"')START_REPLICATION SLOT "sub_pgbench" LOGICAL
0/0 (proto_version '3', publication_names '"pub_pgbench"')
"""
attached the backtrace.
--
Jaime Casanova
Director de Servicios Profesionales
SystemGuards - Consultores
ed.1,id}
rowfilter |
"""
This could be solved by adding a "NOT attisdropped", simple patch
attached.
--
Jaime Casanova
Director de Servicios Profesionales
SystemGuards - Consultores de PostgreSQL
diff --git a/src/backend/catalog/system_views.sql b/src/backend/c
range(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
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 de Pos
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
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 convinced this is actually providi
(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
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
de 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 definition of the states ma
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 12:14
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=6) at
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
ad 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
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/ref/pgupgrade.sgml
+++ b/d
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
""&
erstand 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
mostly kept my patches separate.
> Hopefully this is more helpful than a complication.
> I added at: https://commitfest.postgresql.org/35/3332/
>
Actually, this is confusing. Which patch is the one we should be
reviewing?
--
Jaime Casanova
Director de Servicios Profesionales
SystemGuards - Consultores de PostgreSQL
s
Test Summary Report
---
t/026_overwrite_contrecord.pl (Wstat: 7424 Tests: 1 Failed: 0)
Non-zero exit status: 29
Parse errors: Bad plan. You planned 3 tests but ran 1.
Files=26, Tests=279, 400 wallclock secs ( 0.27 usr 0.10 sys + 73.78 cusr 59.66
csys = 133.81 CPU)
Resu
On Wed, Oct 06, 2021 at 12:21:02AM -0500, Jaime Casanova wrote:
> Hi everyone,
>
> At this time I'm looking to close the CF.
>
Closed
> So, I will write and mark as RwF the patches currently failing on the
> cfbot and move to the next CF all other patches.
>
> Rw
- Introduce ProcessInterrupts_hook for C extensions
- Make message at end-of-recovery less scary
--
Jaime Casanova
Director de Servicios Profesionales
SystemGuards - Consultores de PostgreSQL
On Mon, Oct 04, 2021 at 02:08:58PM -0500, Jaime Casanova wrote:
> Hi,
>
> Here's the list mentioned in ${SUBJECT}, please can the committers
> mention what they want to do with those?
>
To move forward I have moved all RfC entries to next CF
--
Jaime Casanova
Direct
consumption
> by the optimizer shall be released by MemoryContext mechanism.
> If add_path does not release path-node, the above portion is much simpler.
>
Hi Kaigai-san,
Do you have an updated patch? Please feel free to resubmit to next CF.
Current CF entry has been marked as RwF.
--
Jaime Casanova
be renamed as
> > pk_known_equal and pks_known_equal as num_equal_pks.
> >
>
> Thanks for the suggestion. Will do that in the new version of patch.
>
Hi Richard,
We are marking this CF entry as "Returned with Feedback", which means
you are encouraged to sen
On Mon, Oct 04, 2021 at 02:12:49AM -0500, Jaime Casanova wrote:
> On Sun, Oct 03, 2021 at 03:14:58PM -0400, Tom Lane wrote:
> [...]
> >
> > Here's what I found, along with some commentary about each one.
> >
> > Patch Age in CFs
> >
> > Pr
On Tue, Oct 05, 2021 at 03:24:40PM +0900, Etsuro Fujita wrote:
> Hi Jaime,
>
> On Tue, Oct 5, 2021 at 4:09 AM Jaime Casanova
> wrote:
> > - Fast COPY FROM command for the foreign tables
> > Last patch was on Jun-2021, no further activity after that.
> > Etsur
rrently this does not apply to head.
I'll mark this as WoA and move it to necxt CF.
--
Jaime Casanova
Director de Servicios Profesionales
SystemGuards - Consultores de PostgreSQL
> On Mon, Oct 04, 2021 at 04:27:54PM -0500, Jaime Casanova wrote:
>> On Thu, Jun 10, 2021 at 07:14:32PM -0700, Jeff Davis wrote:
>> >
>> > I'll start with the reason I set the work down before: it did not work
>> > well with multiple join keys. That might be fi
ld be a good candidate for the
> CustomScan extension mechanism, which would make it easier to
> experiment with?
>
Hi,
It seems this has been stalled since jun-2021. I intend mark this as
RwF unless someone speaks in the next hour or so.
--
Jaime Casanova
Director de Servicios Profesionales
SystemGuards - Consultores de PostgreSQL
Last patch is from mar-2021. Heikki, are you going to take this one?
Etsuro Fujita:
- Fast COPY FROM command for the foreign tables
Last patch was on Jun-2021, no further activity after that.
Etsuro-san, are you going to commit this soon?
--
Jaime Casanova
Director de Servicios Profesionales
On Mon, Sep 27, 2021 at 04:30:25PM +1300, David Rowley wrote:
> On Fri, 24 Sept 2021 at 20:26, Jaime Casanova
> wrote:
> > Are you planning to work on this in this CF?
> > This is marked as "Ready for committer" but it doesn't apply anymore.
>
> I've attached
ng an
> interest here. Unless somebody intends to take an interest,
> we should put this one out of its misery.
> Proposed action: Reject for lack of interest
>
The author of the patch claimed that a rebased version should happen at
mid-august but it hasn't happened. RwF seems reasonable to me, done
that.
--
Jaime Casanova
Director de Servicios Profesionales
SystemGuards - Consultores de PostgreSQL
On Sun, Oct 03, 2021 at 11:20:21AM -0500, Jaime Casanova wrote:
> On Sat, Oct 02, 2021 at 11:32:01AM -0400, Tom Lane wrote:
> > Alvaro Herrera writes:
> > > On 2021-Oct-02, Tom Lane wrote:
> > >> Yeah. I have been thinking of looking through the oldest CF entrie
gt; (I did have the luxury of a local copy of the commitfest database, which
> is perhaps a service we could offer to CFMs to make their lives easier.)
>
Right now, an option to bulk move everything in their current states to
Next CF would be handy... There are still 139 remaining patches
en stalled more than one
month and after asking in the thread if I receive no answer for 2 or 3
weeks.
--
Jaime Casanova
Director de Servicios Profesionales
SystemGuards - Consultores de PostgreSQL
turned to other sessions accessing the same row. Since this
> > situation is detectable from the syntax and hard to fix otherwise,
> > forbid for now, with the potential to fix in the future.
>
> Thank you, pushed with minimal adjustment.
>
BTW, I just marked this one as com
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
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 we generall
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
se 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 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.
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 entry to t
t. 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 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
roceed
> 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 version of
t;Set 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?
--
Jaime
is still 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
st 78 rows 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
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
der 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
he 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 you on this.
I'm marki
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 stal
as "Ready for committer" but it doesn't apply anymore.
--
Jaime Casanova
Director de Servicios Profesionales
SystemGuards - Consultores de PostgreSQL
ersion 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
idr) = 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 = {419430
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
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 n
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.
--
Jaime
le that 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
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
n=# 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 using syntax ON CO
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
ld 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
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
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 taki
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
Director de Servici
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 app.
&
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
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 cleanly nor com
nce 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
9c5b0) at
bitmapset.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/sql
#0
Hi Á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
.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
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
aul,
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
SystemGuards
razel/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
e 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
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
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 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 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
ss and few bugs.
>
Congrats Daniel and John. Keep your good 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 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.
1 - 100 of 153 matches
Mail list logo
