Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: Rob Sargent <robjsargent@gmail.com>
Mime-Version: 1.0 (1.0)
Subject: Re: Convert date and time colums to datetime
Date: Sun, 19 Oct 2025 20:32:07 -0600
Message-Id: <3F3B9CFD-3901-4689-A38C-84CFA767D02E@gmail.com>
References: <bc4129d5-e25b-ee48-cbd9-93108686837d@appl-ecosys.com>
Cc: pgsql-general@postgresql.org
In-Reply-To: <bc4129d5-e25b-ee48-cbd9-93108686837d@appl-ecosys.com>
To: Rich Shepard <rshepard@appl-ecosys.com>
Archived-At: <https://www.postgresql.org/message-id/3F3B9CFD-3901-4689-A38C-84CFA767D02E%40gmail.com>
Precedence: bulk


> On Oct 19, 2025, at 2:38=E2=80=AFPM, Rich Shepard <rshepard@appl-ecosys.co=
m> wrote:
>=20
> =EF=BB=BFOn Sun, 19 Oct 2025, Rob Sargent wrote:
>=20
>> I think you have to ask why those values were separated in the first
>> place. For instance if they are thought of as a pair in most queries then=

>> an alteration might be in order. There can be a large one time cost if
>> these tables occur in a lot of separate sql calls in the business logic.
>=20
> Rob,
>=20
> Good point. They're in the contacts table and I use them to determine when=

> to make another contact and if prior contacts were more productive in the
> morning or afternoon.
>=20
> Thanks,
>=20
> Rich
>=20
>=20

Definitely a datetime (single value) problem, imho=