Re: Remove an unused function GetWalRcvWriteRecPtr
От
Michael Paquier
Тема
Re: Remove an unused function GetWalRcvWriteRecPtr
Дата
Msg-id
Yj6qHS66HVlr5+v5@paquier.xyz
Ответ на
Remove an unused function GetWalRcvWriteRecPtr (Bharath Rupireddy)
Список
Дерево обсуждения
Remove an unused function GetWalRcvWriteRecPtr Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Re: Remove an unused function GetWalRcvWriteRecPtr Andres Freund <andres@anarazel.de>
Re: Remove an unused function GetWalRcvWriteRecPtr Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Re: Remove an unused function GetWalRcvWriteRecPtr Tom Lane <tgl@sss.pgh.pa.us>
Re: Remove an unused function GetWalRcvWriteRecPtr Michael Paquier <michael@paquier.xyz>
Re: Remove an unused function GetWalRcvWriteRecPtr Julien Rouhaud <rjuju123@gmail.com>
Re: Remove an unused function GetWalRcvWriteRecPtr Tom Lane <tgl@sss.pgh.pa.us>
Re: Remove an unused function GetWalRcvWriteRecPtr Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
On Sat, Mar 26, 2022 at 10:51:15AM +0530, Bharath Rupireddy wrote: > The function GetWalRcvWriteRecPtr isn't being used anywhere, however > pg_atomic_read_u64(&walrcv->writtenUpto); (reading writtenUpto without > spinlock) is being used directly in pg_stat_get_wal_receiver > walreceiver.c. We either make use of the function instead of > pg_atomic_read_u64(&walrcv->writtenUpto); or remove it. Since there's > only one function using walrcv->writtenUpto right now, I prefer to > remove the function to save some LOC (13). > > Attaching patch. Thoughts? This could be used by some external module, no? -- Michael
В списке pgsql-hackers по дате отправления
От: Bharath Rupireddy
Дата:
От: Bharath Rupireddy
Дата: