Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps  (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.96)
	(envelope-from <pgsql-general-owner+archive@lists.postgresql.org>)
	id 1vRFi5-00ASJd-0w
	for pgsql-general@arkaria.postgresql.org;
	Thu, 04 Dec 2025 20:13:53 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.96)
	(envelope-from <pgsql-general-owner+archive@lists.postgresql.org>)
	id 1vRFi4-004dt2-0V
	for pgsql-general@arkaria.postgresql.org;
	Thu, 04 Dec 2025 20:13:52 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps  (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.96)
	(envelope-from <rshepard@appl-ecosys.com>)
	id 1vRFi3-004dse-2d
	for pgsql-general@lists.postgresql.org;
	Thu, 04 Dec 2025 20:13:52 +0000
Received: from mail.appl-ecosys.com ([50.126.108.78])
	by makus.postgresql.org with esmtps  (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.96)
	(envelope-from <rshepard@appl-ecosys.com>)
	id 1vRFi1-0039wl-2G
	for pgsql-general@lists.postgresql.org;
	Thu, 04 Dec 2025 20:13:51 +0000
Received: from salmo.appl-ecosys.com (salmo.appl-ecosys.com [192.168.55.1])
	by mail.appl-ecosys.com (Postfix) with ESMTP id 827532A14D6
	for <pgsql-general@lists.postgresql.org>; Thu,  4 Dec 2025 12:13:49 -0800 (PST)
Date: Thu, 4 Dec 2025 12:13:49 -0800 (PST)
From: Rich Shepard <rshepard@appl-ecosys.com>
To: pgsql-general@lists.postgresql.org
Subject: Re: Extract only maximum date from column
In-Reply-To: <d0606565-1fad-419d-922c-b3e8f76495a6@gmail.com>
Message-ID: <47e11d37-37b-8341-a0c2-45f1b1b7ca9a@appl-ecosys.com>
References: <db81f086-e1a5-5798-f9bd-5bed5b1bc7f4@appl-ecosys.com> <d0606565-1fad-419d-922c-b3e8f76495a6@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
List-Id: <pgsql-general.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-general@lists.postgresql.org>
List-Owner: <mailto:pgsql-general-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-general>
Archived-At: <https://www.postgresql.org/message-id/47e11d37-37b-8341-a0c2-45f1b1b7ca9a%40appl-ecosys.com>
Precedence: bulk

On Thu, 4 Dec 2025, Bryan Sayer wrote:

> I believe in general you need
>
> having c.next_contact = max(c.next_contact)
>
> (at least in ANSI SQL) Use having for after the join has occurred

Bryan,

Postgresql didn't like that regardless of where I inserted the `having'
stanza.

Thanks,

Rich