RE: [EXTERNAL] Any objection to documenting pg_sequence_last_value()? - Mailing list pgsql-hackers

From Hanefi Onaldi
Subject RE: [EXTERNAL] Any objection to documenting pg_sequence_last_value()?
Date
Msg-id DM6PR21MB1497482986C5C773BEEBB064E37D9@DM6PR21MB1497.namprd21.prod.outlook.com
Whole thread Raw
In response to Any objection to documenting pg_sequence_last_value()?  (James Coleman <jtc331@gmail.com>)
Responses Re: [EXTERNAL] Any objection to documenting pg_sequence_last_value()?
List pgsql-hackers
Hi All,

I recently used pg_sequence_last_value() when working on a feature in an extension, and it would have been easier for
meif there were some documentation for this function.
 

I'd like to help document this function if there are no objections.

Best,
Hanefi

-----Original Message-----
From: James Coleman <jtc331@gmail.com> 
Sent: 6 Ağustos 2020 Perşembe 16:14
To: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: [EXTERNAL] Any objection to documenting pg_sequence_last_value()?

The function pg_sequence_last_value() was added to underlie the pg_sequences view, and it's the only way I'm aware of
fromuserspace to directly get the last value of a sequence globally (i.e., not within the current session like
currval()/lastval()).Obviously you can join to the pg_sequences view, but that's sometimes unnecessarily cumbersome
sinceit doesn't expose the relid of the sequence.
 

When that function got added it apparently wasn't added to the docs, though I'm not sure if that was intentional or
not.

Does anyone have any objections to documenting
pg_sequence_last_value() in the sequence manipulation functions doc page?

James



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: [PATCH] Provide more information to filter_prepare
Next
From: "Joel Jacobson"
Date:
Subject: Re: Idea: Avoid JOINs by using path expressions to follow FKs