Postgres Pro
Downloads
Home   >   mailing lists

Are we missing (void) when return value of fsm_set_and_search is ignored? - Mailing list pgsql-hackers

From Bharath Rupireddy
Subject Are we missing (void) when return value of fsm_set_and_search is ignored?
Date
Msg-id CALj2ACXvBxB96yCQETaBmKdTsYXSbFj=BCQAeiOR2ouVM6HuTA@mail.gmail.com
Whole thread Raw
Responses Re: Are we missing (void) when return value of fsm_set_and_search is ignored?
Re: Are we missing (void) when return value of fsm_set_and_search is ignored?
Re: Are we missing (void) when return value of fsm_set_and_search is ignored?
List pgsql-hackers
Tree view 
Hi,

It looks like for some of the fsm_set_and_search calls whose return
value is ignored (in fsm_search and RecordPageWithFreeSpace), there's
no (void). Is it intentional? In the code base, we generally have
(void) when non-void return value of a function is ignored.

Thoughts?

With Regards,
Bharath Rupireddy.

pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: locking [user] catalog tables vs 2pc vs logical rep
Next
From: Daniel Gustafsson
Date:
Subject: Re: pg_upgrade is failed for 'plpgsql_call_handler' handler