Horton

Re: [PATCH] Generate random dates/times in a specified range

Tom Lane <tgl@sss.pgh.pa.us>

View thread
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Vik Fearing <vik@postgresfriends.org>
Cc: Chao Li <li.evan.chao@gmail.com>, Damien Clochard <damien@dalibo.info>, Greg Sabino Mullane <htamfids@gmail.com>, Dean Rasheed <dean.a.rasheed@gmail.com>, pgsql-hackers@lists.postgresql.org
Date: 2025-08-29T14:57:08Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. doc: Improve description of new random(min, max) functions.

  2. Add date and timestamp variants of random(min, max).

Vik Fearing <vik@postgresfriends.org> writes:
> On 29/08/2025 11:12, Chao Li wrote:
>> But a major problem is, I think we should bump CATALOG_VERSION_NO. 

> Traditionally, the patch committer bumps the catversion, not the patch 
> author.

Yeah.  If you include a catversion bump in a submitted patch, you can
expect the patch to break repeatedly while it's sitting in the queue,
due to unrelated patches changing catversion.  So we prefer to have
the committer add that at the last moment.

If you're worried that the committer might forget that, you can
add a comment about it in the patch's draft commit message.

			regards, tom lane