On Mon, Aug 7, 2023 at 3:17 PM Drouvot, Bertrand
wrote:
>
> Hi,
>
> On 8/4/23 1:32 PM, shveta malik wrote:
> > On Fri, Aug 4, 2023 at 2:44 PM Drouvot, Bertrand
> > wrote:
> >> On 7/28/23 4:39 PM, Bharath Rupireddy wrote:
>
> >> Sorry to be late, but I gave a second thought and I wonder if we real
Hi,
I updated the comment in 'SnapshotSetCommandId' in this patch which specifies
the reason why it
is not necessary to update 'curcid' of CatalogSnapshot.
Best regards, xiaoran
0001-Update-the-comment-in-SnapshotSetCommandId.patch
Description: 0001-Update-the-comment-in-SnapshotSetCommandId.p
po 31. 7. 2023 v 17:46 odesílatel Jelte Fennema napsal:
> On Mon, 24 Jul 2023 at 21:16, Pavel Stehule
> wrote:
> > I don't understand how it can be possible to do it without. I need to
> process possible errors, and then I need to read and synchronize protocol.
> I didn't inject
> > this featur
Op 8/8/23 om 03:15 schreef Jonathan S. Katz:
Please provide your feedback no later than August 10, 2023 0:00 AoE[1].
'You us' should be
'You use'
(2x)
Erik
Hi,
On 8/8/23 1:25 AM, Michael Paquier wrote:
On Mon, Aug 07, 2023 at 10:34:43AM +0200, Drouvot, Bertrand wrote:
fa88928470 introduced src/backend/utils/activity/wait_event_names.txt that has
been auto-generated. The auto-generation had parsing errors leading to bad
entries in wait_event_names.
Hi,
On 8/8/23 5:05 AM, Michael Paquier wrote:
On Tue, Aug 08, 2023 at 11:53:32AM +0900, Kyotaro Horiguchi wrote:
As I mentioned in another thread, I'm uncertain about our stance on
the class id of the wait event. If a class acts as a namespace, we
should include it in the view. Otherwise, if th
Hi,
On 8/8/23 7:01 AM, shveta malik wrote:
On Mon, Aug 7, 2023 at 3:17 PM Drouvot, Bertrand
wrote:
Hi,
On 8/4/23 1:32 PM, shveta malik wrote:
On Fri, Aug 4, 2023 at 2:44 PM Drouvot, Bertrand
wrote:
On 7/28/23 4:39 PM, Bharath Rupireddy wrote:
Agreed. That is why in v10,v11 patches, we
On Tue, Aug 01, 2023 at 04:39:54PM -0700, Jeff Davis wrote:
> On Tue, 2023-08-01 at 16:14 +0300, Aleksander Alekseev wrote:
> > Probably I'm missing something, but if memory allocation is required
> > during WAL replay and it fails, wouldn't it be a better solution to
> > log the error and terminat
Hi All,
I have been looking at memory consumed when planning a partitionwise join
[1], [2] and [3]. I am using the attached patch to measure the memory
consumption. The patch has been useful to detect an increased memory
consumption in other patches e.g. [4] and [5]. The patch looks useful by
itsel
Hi Andrey,
On Tue, Aug 8, 2023 at 8:52 AM Andrey Lepikhov
wrote:
> It is a positive thing to access some planner internals from the
> console, of course. My point is dedicated to the structuration of an
> EXPLAIN output and is caused by two reasons:
> 1. I use the EXPLAIN command daily to identif
On 2023-Aug-07, Nathan Bossart wrote:
> On Mon, Aug 07, 2023 at 04:02:08PM -0400, Tom Lane wrote:
> > Dave Cramer writes:
> >> Can we vote or whatever it takes to decide on a naming pattern that is
> >> acceptable ?
> >
> > I'm good with Robert's proposal above.
>
> +1
WFM as well.
--
Álvar
On Tue, Aug 8, 2023 at 10:07 AM YANG Xudong wrote:
> On 2023/8/7 19:01, John Naylor wrote:
> > The compilation test is found in c-compiler.m4, which still has all
> > logic for CFLAGS_CRC, including saving and restoring the old CFLAGS. Can
> > this also be simplified?
>
> Fixed the function in c
On Tue, Aug 8, 2023 at 12:53 AM Robert Haas wrote:
> On Mon, Aug 7, 2023 at 10:25 AM Amit Langote wrote:
> > Note we’re talking here about “initial” pruning that occurs during
> > ExecInitNode(). Workers are only launched during ExecGather[Merge]() which
> > thereafter do ExecInitNode() on thei
101 - 113 of 113 matches
Mail list logo