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.94.2) (envelope-from ) id 1uzRIG-003UYd-L5 for pgsql-general@arkaria.postgresql.org; Fri, 19 Sep 2025 02:56:16 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1uzRID-003U9D-CC for pgsql-general@arkaria.postgresql.org; Fri, 19 Sep 2025 02:56:13 +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.94.2) (envelope-from ) id 1uzRID-003U92-17 for pgsql-general@lists.postgresql.org; Fri, 19 Sep 2025 02:56:13 +0000 Received: from mail-io1-xd2f.google.com ([2607:f8b0:4864:20::d2f]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1uzRIA-001C8N-2v for pgsql-general@lists.postgresql.org; Fri, 19 Sep 2025 02:56:12 +0000 Received: by mail-io1-xd2f.google.com with SMTP id ca18e2360f4ac-8a72cb326c0so1556339f.0 for ; Thu, 18 Sep 2025 19:56:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1758250569; x=1758855369; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=LV7ZdbXgeothPXVlcvt1fl0OUUFl5wxNuVj7fza6fiU=; b=ZcZcXjKn3lwZadDylzxOqgy/dtY+mkbdrnCKo/BO8Y7fKgc0eBU0n7lrGVrvfO9+cG HUAchPfayQThu2StQmEx97fBnrLXCxCDVnpkjSbD7pmfWYtugnRx5YWvFZOzvgxW9A0J 2db38sLbgTjWSNG50SCdFsbdxkZJceRViEXeut9+af3zr/uQcM06NGC/JpzsQm9edml3 zO71RlQMtYGGfeNpIN34iY0fqf0DU966s8wxxR/J3l0gEUOrcCw7u45xyJ+1pMrsCmil HrqMhLDFJoeADLz98ovqRfbJyzO+GOxytFCUmqKJbXmmq2DNvLnUJxqu903ag3VtJJkb bICA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1758250569; x=1758855369; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=LV7ZdbXgeothPXVlcvt1fl0OUUFl5wxNuVj7fza6fiU=; b=wEkoJQXGsf8vW5OpsPG/teJ5wax/xeaYGoU/PiGDwwChJQhFfYO9Hkrl3iv5rtePuR vZmHtayPaKdJQllA4Kwb+E1IqIcJIeSyzbouTNgsVeLceuI7tjTc+SFE5APhnhoYJ4FL XwSi2QNIpf2+kr3haMlATiDdvSR/sctfpDni7tdZl6jcWxMhaKFTOEemlNrOvqWu9VOz LsW5ayhQmGN9jv4h+e2YJbXaHEHeabmJl5Xjmei5UCJrg8X6f5Bcypk9NQLwOcQ0IWXr L7ATkKcy+2rk8lNLPLif7G6/YYU6KQMBYFi7NqMCeSNIAl3Gu20he2CgANpCsoYB18YQ Sx0Q== X-Gm-Message-State: AOJu0YynD37pCFzEIdHwuK700uaUK7neq7pfPn8B8kqpT45S6CfKwZ1v R1c51QtbZt2wFwVfWTHxe2Z344spVe9SPlEgiNIZtG/gcG2VTE0FSOhQzfUMFbWuPDcByCBEHFQ qOz/9YSpaSkJpQ0wl4EzaaeiJC6qaVP/EFA== X-Gm-Gg: ASbGncs2JJLKHo8NuisfEUQy17F1OlIg334lW5rHKrYdSk7/y40uXT/HA+rl14OnNUG /7+NihRrJdxj9x0xaGM4p3LZf69xoNObEfrgoz7MjCAXc+TxDLtNeNLYC4sKOD8hTrGvwVmUHUJ NZij08rHjUokk1Hb1MbSYFH+7ner0BIjbSx/wRiO69tIKU8HZByXLMmO6VRmBfRDHIn/epSTVCu 37qW5bCtrPIG1s2s4ylfL4w5cgEow52Ilz4QV9K X-Google-Smtp-Source: AGHT+IFv2pJQi/8sY6V24rjf1cOObGgIpB5Y7yv8JAIENKCFA31xA31JwkA0Oe5LtL5iX/Whh4bFC2epwUANcN3J1tQ= X-Received: by 2002:a05:6e02:1b07:b0:424:2357:d75 with SMTP id e9e14a558f8ab-4248198a968mr11387965ab.3.1758250569358; Thu, 18 Sep 2025 19:56:09 -0700 (PDT) MIME-Version: 1.0 From: =?UTF-8?B?5by15a6455GL?= Date: Fri, 19 Sep 2025 10:55:58 +0800 X-Gm-Features: AS18NWCT9DGzC6Dss8FiPP6n1MDCU3d6jEMy2g90PdX5mrvRscENuBcNbCBK16c Message-ID: Subject: PostgreSQL Account and Object Timestamp Logging To: pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="0000000000009ce62f063f1e9cad" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000009ce62f063f1e9cad Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello everyone, I would like to ask if there are any built-in features or extensions in open-source PostgreSQL=E2=80=94aside from the AUDIT mechanisms=E2=80=94that= allow us to query or log the creation time of user accounts and database objects. The reason for this inquiry is that while audit logs do capture these events, they may eventually be rotated out or removed due to housekeeping policies. Having a dedicated table or view to permanently record the creation or modification time of accounts and objects would be very helpful for audit and security compliance purposes. Thank you in advance for your insights! --0000000000009ce62f063f1e9cad Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello everyone,

I would like to ask if there are any built-in f= eatures or extensions in open-source PostgreSQL=E2=80=94aside from the AUDI= T mechanisms=E2=80=94that allow us to query or log the creation time of use= r accounts and database objects.

The reason for this inquiry is that= while audit logs do capture these events, they may eventually be rotated o= ut or removed due to housekeeping policies. Having a dedicated table or vie= w to permanently record the creation or modification time of accounts and o= bjects would be very helpful for audit and security compliance purposes.
Thank you in advance for your insights!
--0000000000009ce62f063f1e9cad--