Dong Wook Lee writes:
> I wrote a test of the old_snapshot extension for coverage.
Hmm, does this really provide any meaningful coverage? The test
sure looks like it's not doing much.
I spent some time a week or so ago trying to graft testing of
contrib/old_snapshot into
On Fri, Jul 29, 2022 at 10:51 AM vignesh C wrote:
>
> On Fri, Jul 29, 2022 at 8:31 AM Peter Smith wrote:
> >
> > Here are some comments for the patch v40-0001:
> >
> > ==
> >
> > 1. Commit message
> >
> > It might be better to always use 'copy_data = true' in favour of
> > 'copy_data = on'
On Tue, Aug 2, 2022 at 5:16 PM houzj.f...@fujitsu.com
wrote:
>
> On Wednesday, July 27, 2022 4:22 PM houzj.f...@fujitsu.com wrote:
> >
> > On Tuesday, July 26, 2022 5:34 PM Dilip Kumar
> > wrote:
> >
> > > 3.
> > > Why are we restricting parallel apply workers only for the streamed
> > >
On Thu, Aug 4, 2022 at 9:57 AM Bharath Rupireddy
wrote:
>
> On Wed, Aug 3, 2022 at 12:11 AM Robert Haas wrote:
> >
> > On Tue, Aug 2, 2022 at 3:25 AM Bharath Rupireddy
> > wrote:
> > > ereport_startup_progress infrastructure added by commit 9ce346e [1]
> > > will be super-useful for reporting
At Fri, 5 Aug 2022 21:28:16 +, "Imseih (AWS), Sami"
wrote in
> > Would you mind trying the second attached to abtain detailed log on
> > your testing environment? With the patch, the modified TAP test yields
> > the log lines like below.
>
> I applied the logging patch to 13.7 ( attached
On Wed, Aug 3, 2022 at 1:20 PM Masahiko Sawada wrote:
>
> On Wed, Aug 3, 2022 at 3:52 PM shiy.f...@fujitsu.com
> wrote:
> >
> > On Wed, Aug 3, 2022 12:06 PM Masahiko Sawada wrote:
> > >
> > > I've attached updated patches that incorporated the above comments as
> > > well as the comments from
Hi hackers,
I wrote a test of the old_snapshot extension for coverage.
I hope that this is written correctly.
before:
0%
after:
100%
---
regards,
Lee Dong Wook.
v1_add_test_oldsnapshot.patch
Description: Binary data
Thomas Munro writes:
> On Thu, Aug 4, 2022 at 4:09 PM Tom Lane wrote:
>> clock_gettime is required by SUSv2 (1997), so I have to admit that
>> macOS 10.4 doesn't have a lot of excuse not to have it. In any case,
>> prairiedog is just sitting there doing its thing until I find cycles
>> to
On Mon, Aug 8, 2022 at 7:12 AM Noah Misch wrote:
> On Sun, Aug 07, 2022 at 03:18:52PM +0200, Tomas Vondra wrote:
> > I'd bet it's about WAL prefetching, not the revert, and the bisect was a
> > bit incorrect, because the commits are close and the failures happen to
> > be rare. (Presumably you
On Sun, Aug 07, 2022 at 03:18:52PM +0200, Tomas Vondra wrote:
> On 8/7/22 02:36, Noah Misch wrote:
> > On Thu, Apr 07, 2022 at 08:34:50PM +0200, Tomas Vondra wrote:
> >> I've pushed a revert af all the commits related to this - decoding of
> >> sequences and test_decoding / built-in replication
Hi,
On 2022-08-06 18:29:14 -0700, Andres Freund wrote:
> 0003: aix: aix3.2.5, aix4.1 are not even of historical interest at this point
> - 4.1 was released before the first commit in our commit history
hoverfly clearly doesn't like this:
Hi,
On 2022-08-07 11:56:44 -0300, Marcos Pegoraro wrote:
> it´s csvlog only
How are you running postgres? If the logger process runs into trouble it might
write to stderr.
Is there a chance your huge statements would make you run out of space?
Greetings,
Andres Freund
> On 7 Aug 2022, at 06:39, Bharath Rupireddy
> wrote:
>
> Agree. Why can't we just prefetch the entire WAL file once whenever it
> is opened for the first time? Does the OS have any limitations on max
> size to prefetch at once? It may sound aggressive, but it avoids
> fadvise() system
On Sun, Aug 7, 2022 at 3:19 PM Thomas Munro wrote:
>
> > A second thing is that pg_pwritev_with_retry_and_write_zeros() is
> > designed to work on WAL segments initialization and it uses
> > XLOG_BLCKSZ and PGAlignedXLogBlock for the job, but there is nothing
> > in its name that tells us so.
it´s csvlog only
Atenciosamente,
Em dom., 7 de ago. de 2022 às 11:12, Tom Lane escreveu:
> Marcos Pegoraro writes:
> > I have to fix log files because its content is not properly formatted,
>
> What mechanism are you using to store the log? If syslog is involved,
> it's reputed to drop
Amit Kapila writes:
> On Wed, Aug 3, 2022 at 7:16 PM Tom Lane wrote:
>> More likely, we need to add something explicit to Mkvcbuild.pm
>> for this. I recall that it has stanzas to deal with updating
>> other autogenerated files; I bet we either missed that or
>> fat-fingered it for
Marcos Pegoraro writes:
> I have to fix log files because its content is not properly formatted,
What mechanism are you using to store the log? If syslog is involved,
it's reputed to drop data under load.
regards, tom lane
On Sun, 7 Aug 2022 at 09:58, Robert Haas wrote:
> On Wed, Mar 24, 2021 at 12:01 PM Tom Lane wrote:
> > I don't think I buy the premise that there are exactly two levels
> > on the client side.
>
> Thanks for sharing your thoughts on this. I agree it's a complex
> issue, and the idea that there
I have to fix log files because its content is not properly formatted, I´m
using version 14.4 but that happened when I was using version 11 too. It
happens only when that statement is huge, or because it is a long sequence
of updates in a WITH or DO statements, or because i´m updating a bytea
On 8/7/22 02:36, Noah Misch wrote:
> On Thu, Apr 07, 2022 at 08:34:50PM +0200, Tomas Vondra wrote:
>> I've pushed a revert af all the commits related to this - decoding of
>> sequences and test_decoding / built-in replication changes.
>
> Two July buildfarm runs failed with PANIC during
On Sun, Aug 7, 2022 at 7:56 PM Michael Paquier wrote:
> FWIW, when it comes to that we have a couple of routines that just use
> '0' to mean such a thing, aka palloc0(). I find 0002 confusing, as it
> introduces in fe_utils.c a new wrapper
> (pg_pwritev_with_retry_and_write_zeros) on what's
On Sun, Aug 07, 2022 at 10:41:49AM +0530, Bharath Rupireddy wrote:
> Agree. I separated out the changes.
+
+/*
+ * A convenience wrapper for pwritev() that retries on partial write. If an
+ * error is returned, it is unspecified how much has been written.
+ */
+ssize_t
+pg_pwritev_with_retry(int
On Sun, Aug 7, 2022 at 7:05 AM Tom Lane wrote:
> Even on a modern Linux:
>
> $ size src/backend/parser/gram.o
>textdata bss dec hex filename
> 656568 0 0 656568 a04b8 src/backend/parser/gram.o
> $ size src/interfaces/ecpg/preproc/preproc.o
>textdata
On Sat, Aug 06, 2022 at 10:59:26AM -0400, Joe Conway wrote:
> I am not sure how else we should interpret SYSTEM_USER -- if it isn't
> port->authn_id what else would you propose it should be?
What you say sounds rather right, but I was wondering mainly what
Oracle and SQL server report when it
Hi,
On 2022-08-06 23:20:26 -0700, Andres Freund wrote:
> The good: That is just because we haven't applied enough, or the right,
> magic. To have mingw to not interfere with things one also has to pass
> -D_UCRT and -lucrt - then the tests pass, even without HAVE_BUGGY_STRTOF.
Looks like only
Hi,
On 2022-08-07 01:17:22 -0400, Tom Lane wrote:
> Andres Freund writes:
> > On 2022-08-06 22:55:14 -0400, Tom Lane wrote:
> >> IMO, it'd be entirely reasonable for Andres to say that *he* doesn't
> >> want to fix the meson build scripts for niche platform X. Then
> >> it'd be up to people who
Hi,
On 2022-08-06 20:39:48 -0700, Andres Freund wrote:
> On 2022-08-06 22:58:12 -0400, Tom Lane wrote:
> > You could pull it out and see if the buildfarm breaks, but my money
> > is on it breaking. That HAVE_BUGGY_STRTOF stuff isn't very old.
>
> We only recently figured out that we should use
27 matches
Mail list logo
