| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Alexander Lakhin <exclusion(at)gmail(dot)com>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de>, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
| Subject: | Re: Recent 027_streaming_regress.pl hangs |
| Date: | 2024-08-12 17:21:04 |
| Message-ID: | 683543.1723483264@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> On 2024-08-11 Su 8:32 PM, Tom Lane wrote:
>> I think we need more data. We know that the
>> wait_for_catchup query is never getting to true:
>>
>> SELECT '$target_lsn' <= ${mode}_lsn AND state = 'streaming'
>>
>> but we don't know if the LSN condition or the state condition is
>> what is failing. And if it is the LSN condition, it'd be good
>> to see the actual last LSN, so we can look for patterns like
>> whether there is a page boundary crossing involved. So I suggest
>> adding something like the attached.
> Seems reasonable.
Pushed. In the event I made it just "SELECT * FROM" the relevant
view: there will be few if any rows that aren't potentially
interesting, and filtering the columns doesn't seem like a
forward-looking idea either.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Doruk Yilmaz | 2024-08-12 18:43:48 | [Patch] add new parameter to pg_replication_origin_session_setup |
| Previous Message | Robert Haas | 2024-08-12 16:28:29 | Re: [patch] Imporve pqmq |