Re: Why is parula failing?

On Tue, 14 May 2024 at 08:55, David Rowley wrote: > I've not seen any recent failures from Parula that relate to this > issue. The last one seems to have been about 4 weeks ago. > > I'm now wondering if it's time to revert the debugging code added in > 1db689715. Does anyone think differently?

Re: Why is parula failing?

On Mon, 15 Apr 2024 at 16:02, Tom Lane wrote: > David Rowley writes: > > If GetNowFloat() somehow was returning a negative number then we could > > end up with a large delay. But if gettimeofday() was so badly broken > > then wouldn't there be some evidence of this in the log timestamps on > >

Re: Why is parula failing?

On Mon, 15 Apr 2024 at 14:55, David Rowley wrote: > If GetNowFloat() somehow was returning a negative number then we could > end up with a large delay. But if gettimeofday() was so badly broken > then wouldn't there be some evidence of this in the log timestamps on > failing runs? 3 things

Re: Why is parula failing?

On Sun, 14 Apr 2024 at 00:12, Tom Lane wrote: > If we were only supposed to sleep 0.1 seconds, how is it waiting > for 60 ms (and, presumably, repeating that)? The logic in > pg_sleep is pretty simple, and it's hard to think of anything except > the system clock jumping (far) backwards that

Re: Why is parula failing?

On Mon, 8 Apr 2024 at 21:25, Robins Tharakan wrote: > > > I'll keep an eye on this instance more often for the next few days. > (Let me know if I could capture more if a run gets stuck again) HEAD is stuck again on pg_sleep(), no CPU for the past hour or so. Stack trace seems t

Re: Why is parula failing?

On Wed, 10 Apr 2024 at 10:24, David Rowley wrote: > > Master failed today for the first time since the compiler upgrade. > Again reltuples == 48. Here's what I can add over the past few days: - Almost all failures are either reltuples=48 or SIGABRTs - Almost all SIGABRTs are DDLs - CREATE INDEX

Re: Why is parula failing?

On Wed, 10 Apr 2024 at 10:24, David Rowley wrote: > Master failed today for the first time since the compiler upgrade. > Again reltuples == 48. >From the buildfarm members page, parula seems to be the only aarch64 + gcc 13.2 combination today, and then I suspect whether this is about gcc v13.2

Re: Why is parula failing?

On Tue, 2 Apr 2024 at 15:01, Tom Lane wrote: > "Tharakan, Robins" writes: > > So although HEAD ran fine, but I saw multiple failures (v12, v13, v16) all of which passed on subsequent-tries, > > of which some were even"signal 6: Aborted". > > Ugh... parula didn't send any reports to buildfarm

Re: pg_upgrade failing for 200+ million Large Objects

On Thu, 28 Dec 2023 at 01:48, Tom Lane wrote: > Robins Tharakan writes: > > Applying all 4 patches, I also see good performance improvement. > > With more Large Objects, although pg_dump improved significantly, > > pg_restore is now comfortably an order of magnitude faste

Re: postgres_fdw uninterruptible during connection establishment / ProcSignalBarrier

80) at fe-connect.c:4096 #5 0x7fb7bc097d55 in PQfinish (conn=0x55b191aa9380) at fe-connect.c:4134 #6 0x7fb7bc14a42b in libpqsrv_disconnect (conn=0x55b191aa9380) at ../../src/include/libpq/libpq-be-fe-helpers.h:117 #7 0x00007fb7bc14adf1 in dblink_disconnect (fcinfo=0x55b193894f00) at dblink.c:357 Thanks to SQLSmith for helping with this find. - Robins Tharakan Amazon Web Services

Missing CFI in iterate_word_similarity()

ectly leading me to this scenario. - Robins Tharakan Amazon Web Services Patch applied to commit - 80d690721973f6a031143a24a34b78a0225101a2 SQL repro script CREATE EXTENSION IF NOT EXISTS pg_trgm; set statement_timeout = '1s'; show statement_timeout; \timing on select 1 where re

autoprewarm worker failing to load

prewarm/autoprewarm.c @@ -82,7 +82,7 @@ typedef struct AutoPrewarmSharedState int prewarmed_blocks; } AutoPrewarmSharedState; -void autoprewarm_main(Datum main_arg); +PGDLLEXPORT void autoprewarm_main(Datum main_arg); void autoprewarm_database_main(Datum main_arg); PG_FUNCTION_INFO_V1(autopr

Re: 13dev failed assert: comparetup_index_btree(): ItemPointer values should never be equal

ndRun (port=0x55bfa19218a0) at postmaster.c:4504 #26 0x55bf9fb52778 in BackendStartup (port=0x55bfa19218a0) at postmaster.c:4232 #27 0x55bf9fb4ea5e in ServerLoop () at postmaster.c:1806 #28 0x55bf9fb4e1f7 in PostmasterMain (argc=3, argv=0x55bfa18e9830) at postmaster.c:1478 #29 0x55bf9fa3f864 in main (argc=3, argv=0x55bfa18e9830) at main.c:202 - Robins Tharakan Amazon Web Services

Re: buildfarm instance bichir stuck

On Fri, 9 Apr 2021 at 16:12, Thomas Munro wrote: > From your description it sounds like signals are not arriving at all, > rather than some more complicated race. Let's go back to basics... > what does the attached program print for you? I see: > > tmunro@x1:~/junk$ cc test-signalfd.c >

Re: buildfarm instance bichir stuck

options if required). On Wed, 7 Apr 2021 at 21:49, Andrew Dunstan wrote: > On 4/7/21 2:16 AM, Thomas Munro wrote: > > On Wed, Apr 7, 2021 at 5:44 PM Robins Tharakan wrote: > >> Bichir's been stuck for the past month and is unable to run regression tests since 6a2a70a02018d6362f9841

Re: buildfarm instance bichir stuck

Hi Thomas, Thanks for taking a look at this promptly. On Wed, 7 Apr 2021 at 16:17, Thomas Munro wrote: > On Wed, Apr 7, 2021 at 5:44 PM Robins Tharakan wrote: > > It is interesting that that commit's a month old and probably no other client has complained since, but diving in,

buildfarm instance bichir stuck

Hi, Bichir's been stuck for the past month and is unable to run regression tests since 6a2a70a02018d6362f9841cc2f499cc45405e86b. It is interesting that that commit's a month old and probably no other client has complained since, but diving in, I can see that it's been unable to even start

Re: pg_upgrade failing for 200+ million Large Objects

> Thanks for highlighting the cause here. Hopefully switching mail clients would help. - Robins Tharakan

Re: Brazil disables DST - 2019b update

On Fri, 12 Jul 2019 at 14:04, Michael Paquier wrote: > On Fri, Jul 12, 2019 at 01:42:59PM +1000, Robins Tharakan wrote: > So 2019b has been released on the 1st of July. Usually tzdata updates > happen just before a minor release, so this would get pulled in at the > beginning of A

Brazil disables DST - 2019b update

Hi, The 2019b DST update [1] disables DST for Brazil. This would take effect starting November 2019. The last DST update in Postgres was 2019a in v11.3 (since this update came in after the recent-most Postgres release). Since a ~3 month release cycle may be too close for some users, are there

Re: Typo in recent commit

On 9 December 2017 at 16:11, Magnus Hagander wrote: > ​​ > > Thanks, fixed for the report. > > Thanks Magnus. However, although it was backpatched correctly, looks like the fix on master missed out identity.out related fix.​ Ref:

Typo in recent commit

Hi, Looks like a minor typo in the recent commit. s/identify/identity/ https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=a2c6cf36608e10aa223fef49323b5feba344bfcf - robins | mobile