Re: generate_series for timestamptz and time zone problem
Przemysław Sztoch <przemyslaw@sztoch.pl>
From: Przemysław Sztoch <przemyslaw@sztoch.pl>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Gurjeet Singh <gurjeet@singh.im>,
Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2022-07-04T11:00:03Z
Lists: pgsql-hackers
Attachments
- generate_series_with_timezone_date_trunc_v5.patch (text/plain) patch v5
Tom Lane wrote on 04.07.2022 00:31: > =?UTF-8?Q?Przemys=c5=82aw_Sztoch?= <przemyslaw@sztoch.pl> writes: >> I have problem with this: >> -- Considering only built-in procs (prolang = 12), look for multiple uses >> -- of the same internal function (ie, matching prosrc fields). It's OK to >> -- have several entries with different pronames for the same internal >> function, >> -- but conflicts in the number of arguments and other critical items should >> -- be complained of. (We don't check data types here; see next query.) > It's telling you you're violating project style. Don't make multiple > pg_proc entries point at the same C function and then use PG_NARGS > to disambiguate; instead point at two separate functions. The functions > can share code at the next level down, if they want. (Just looking > at the patch, though, I wonder if sharing code is really beneficial > in this case. It seems quite messy, and I wouldn't be surprised > if it hurts performance in the existing case.) > > You also need to expend some more effort on refactoring code, to > eliminate silliness like looking up the timezone name each time > through the SRF. That's got to be pretty awful performance-wise. > > regards, tom lane Thx. Code is refactored. It is better, now. -- Przemysław Sztoch | Mobile +48 509 99 00 66
Commits
-
Add functions to do timestamptz arithmetic in a non-default timezone.
- 75bd846b68b0 16.0 landed
-
Refactor datetime functions' timezone lookup code to reduce duplication.
- 3e59e5048d0f 16.0 landed
-
Fix volatility marking of timestamptz_trunc_zone.
- 533e02e927c6 16.0 landed