Re: [EXTERNAL] Any objection to documenting pg_sequence_last_value()?
От | James Coleman |
---|---|
Тема | Re: [EXTERNAL] Any objection to documenting pg_sequence_last_value()? |
Дата | |
Msg-id | CAAaqYe_YXrkpLb2xZ0Vxi9hNnwn6tDeE3XAHw1YN8boBjaNX4Q@mail.gmail.com обсуждение исходный текст |
Ответ на | RE: [EXTERNAL] Any objection to documenting pg_sequence_last_value()? (Hanefi Onaldi <Hanefi.Onaldi@microsoft.com>) |
Список | pgsql-hackers |
On Tue, Mar 30, 2021 at 4:37 AM Hanefi Onaldi <Hanefi.Onaldi@microsoft.com> wrote: > > 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 > > Given there's been no objection, I think it'd be worth submitting a patch (and I'd be happy to review if you're willing to author one). James
В списке pgsql-hackers по дате отправления: