pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Justin Pryzby <pryzby@telsasoft.com>
To: Pavel Borisov <pashkin.elfe@gmail.com>
Cc: Maxim Orlov <orlovmg@gmail.com>
Cc: Aleksander Alekseev <aleksander@timescale.com>
Cc: pgsql-hackers@lists.postgresql.org, Stephen Frost <sfrost@snowman.net>
Cc: Alexander Korotkov <aekorotkov@gmail.com>
Cc: Andres Freund <andres@anarazel.de>
Cc: Ilya Anfimov <ilan@tzirechnoy.com>
Subject: Re: Add 64-bit XIDs into PostgreSQL 15
Date: Fri, 15 Jul 2022 07:16:58 -0500
Message-ID: <20220715121658.GI18011@telsasoft.com> (raw)
In-Reply-To: <CALT9ZEFmpuCT65vXZVN=axxoKTr6xjj-kDGNa=KXvMuCfbOcbQ@mail.gmail.com>
References: <CALT9ZEGpr3WEPFJL_EHtzE-vF09SPYeAVyoPYZUuG1=yX5oi+w@mail.gmail.com>
	<CALT9ZEE3aMAT+sATzPEzrti+DZwBse+9+XoiuKkGJV5k=5TrFw@mail.gmail.com>
	<20220701025335.GA13040@telsasoft.com>
	<CALT9ZEEg+efQ8nzt3Fn+vHdH19WOAzdACAZtxe9_8_96n+kXNw@mail.gmail.com>
	<CACG=eza0tv5H4mA+UF_Vk7_cPSQ6kFbzSxKFTuR1o=jmLoo9UQ@mail.gmail.com>
	<CACG=ezYfMkhEZOAV8b2Cmr16hsb9U3mZv+=8NT1Ox6A0u5L_Sg@mail.gmail.com>
	<CACG=ezb_YRCg94BUVqAGWjk-4M-LZOHVvFfcXSt3-acRr2xhyg@mail.gmail.com>
	<CACG=ezY5NFXTRWRdZwWn4BduvLMmOxRCU+aa4=bHB+1YZpnWAg@mail.gmail.com>
	<CALT9ZEE9+n_SE4_=jtmisah4wfB990DgVDzf2PwVOce-6kQ8QA@mail.gmail.com>
	<CALT9ZEFmpuCT65vXZVN=axxoKTr6xjj-kDGNa=KXvMuCfbOcbQ@mail.gmail.com>

On Fri, Jul 15, 2022 at 03:23:29PM +0400, Pavel Borisov wrote:
> On Fri, 15 Jul 2022 at 15:20, Pavel Borisov <pashkin.elfe@gmail.com> wrote:
> > Hi, hackers!
> > v42 stopped applying, so we rebased it to v43. Attached is a GitHub link,
> > but I see Cfbot hasn't become green. Apparently, it hasn't seen changes in
> > GitHub link relative to v42 attached as a patch.
> 
> Github link is as follows:
> https://github.com/ziva777/postgres/tree/64xid-cf
> Maybe this will enable CFbot to see it.

My suggestion was a bit ambiguous, sorry for the confusion.

The "Git link" is just an annotation - cfbot doesn't try to do anything with
it[0] (but cirrusci will run the same checks under your github account).
What I meant was that it doesn't seem imporant to send rebases multiple times
per week if there's been no other changes.  Anyone is still able to review the
patch.  It's possible to build it by applying the patch to a checkout of the
postgres tree at the time the patch was sent.  Or by using the git link.  Or by
checking out cfbot's branch here, from the last time it *did* apply.
https://github.com/postgresql-cfbot/postgresql/tree/commitfest/38/3594

[0] (I think cfbot *could* try to read the git link, and apply patches that it
finds there, but that's an idea that hasn't been proposed or discussed.  It'd
need to know which branch to use, and it'd need to know when to use the git
link and when to use the most-recent email attachments).

-- 
Justin





view thread (232+ messages)  latest in thread

Message-ID: <20220715121658.GI18011@telsasoft.com>
Permalink:  ../20220715121658.GI18011@telsasoft.com/
Also on:    postgresql.org/message-id/20220715121658.GI18011@telsasoft.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: pryzby@telsasoft.com, pashkin.elfe@gmail.com, orlovmg@gmail.com, aleksander@timescale.com, sfrost@snowman.net, aekorotkov@gmail.com, andres@anarazel.de, ilan@tzirechnoy.com
  Subject: Re: Add 64-bit XIDs into PostgreSQL 15
  In-Reply-To: <20220715121658.GI18011@telsasoft.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox