| From: | Kartyshov Ivan <i(dot)kartyshov(at)postgrespro(dot)ru> |
|---|---|
| To: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
| Cc: | Andy Fan <zhihuifan1213(at)163(dot)com>, Alexander Korotkov <aekorotkov(at)gmail(dot)com>, Euler Taveira <euler(at)eulerto(dot)com>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Peter Eisentraut <peter(at)eisentraut(dot)org>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Dilip Kumar <dilipbalaut(at)gmail(dot)com>, Peter Smith <smithpb2250(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: [HACKERS] make async slave to wait for lsn to be replayed |
| Date: | 2024-04-02 15:21:34 |
| Message-ID: | 929e86cb46190f3f42388b942dfec79a@postgrespro.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2024-04-02 13:15, Bharath Rupireddy wrote:
> On Tue, Apr 2, 2024 at 3:41 PM Kartyshov Ivan
> <i(dot)kartyshov(at)postgrespro(dot)ru> wrote:
>>
>> 8 years, we tried to add this feature, and now we suggest the best way
>> for this feature is to commit the minimal version first.
>
> Just curious, do you or anyone else have an immediate use for this
> function? If yes, how are they achieving read-after-write-consistency
> on streaming standbys in their application right now without a
> function like this?
Just now, application runs pg_current_wal_lsn() after update and then
waits on loop pg_current_wal_flush_lsn() until updated.
Or use slow synchronous_commit.
--
Ivan Kartyshov
Postgres Professional: www.postgrespro.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | ShadowGhost | 2024-04-02 15:43:09 | Re: Extension for PostgreSQL cast jsonb to hstore WIP |
| Previous Message | Jeff Davis | 2024-04-02 15:17:10 | Re: Table AM Interface Enhancements |