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 1tNPFb-00AnJR-RQ for pgsql-hackers@arkaria.postgresql.org; Tue, 17 Dec 2024 04:32:03 +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 1tNPFZ-00Ekut-0Y for pgsql-hackers@arkaria.postgresql.org; Tue, 17 Dec 2024 04:32:02 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tNPFY-00Ekuk-MB for pgsql-hackers@lists.postgresql.org; Tue, 17 Dec 2024 04:32:01 +0000 Received: from mail-lj1-x236.google.com ([2a00:1450:4864:20::236]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tNPFX-0005VL-A9 for pgsql-hackers@lists.postgresql.org; Tue, 17 Dec 2024 04:32:01 +0000 Received: by mail-lj1-x236.google.com with SMTP id 38308e7fff4ca-3011c7b39c7so53330971fa.1 for ; Mon, 16 Dec 2024 20:31:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1734409918; x=1735014718; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=Kw0GTXthgI1IrgjXF+Xe2ru66gxeUwhjewBSCXHEor4=; b=VAIe5Y/aYWxbB0t6VxXsFIk4NqNbhBzd0gqJk9QgbUIf9j9r1zPo5X50JNPQVo632h jAYQFn5cCx9wq/yuMnTO61SREEgbeFSl5c+FU8CClt2xeQTjm45vk1iV9J+l3jZ0gFmr mpU4eUbpNmWFN6oDdDZHPNe6ttChsa4VaVmuBSKsygVxZDlqX6ocj554fesMS/uyNeH7 nwbWooySN7TYTjrhX2QNMNvG3t/8Io4Uve60rOoeIMNlA4xCi226OoNbfBmdz6lpwv7C Ot7rZg/xjE34Oh/fnBU20lUPp+GKzVKSTMPUd4HaaNmtu52cQ4SwqedwrKggNQ6C0gFX HfRQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1734409918; x=1735014718; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=Kw0GTXthgI1IrgjXF+Xe2ru66gxeUwhjewBSCXHEor4=; b=Cfmbq6CM8bXgSFkzxjK6uR0pfPYtPqDpBzgFD8zyIBamI6Gp2N+yu+Ba5h9bIzxxi7 6d/+lxX/WAF+4qANiVWg8rWRuhyq+SYOFOoepTtf6AxSK0Dbq5ex1gmkr2U6r79zYNcW Ik3ZP3uhtGUYmWh+t14w0uheseqU2A2HwPCTc2Dacmyh3ljAecj8scuUEocd/dtJRJ2N /qy5Ev2JyhsbZoH21KH4xInuV4TuNa7Y7WI2ZuTYLV/ZjwWTNecuOY1ydoBSh0JFBohW QeSl222tOKsCqWkgCfICynLn3TwxLVLU4kgNKIsvXnJjTJXwxko/mzzsoZ0Lm+wcJYsG vcsg== X-Forwarded-Encrypted: i=1; AJvYcCVYghinKltMMiVnk+PixKCk8O+ooTdah0fs5E1L93ZJpd7+3vTd/U08k9sL21nq3DYxTLcJQrlzD143Cmx4@lists.postgresql.org X-Gm-Message-State: AOJu0Yww0mhT2+jcNfvqmijl9L8a/QSz/HtxxaMDpzd6jH5kk9XDY/m1 b7TL6vL4w0kaAtNQvXTb5UOowtlwyMEBIj8rhXXsOW733QRoq0RLl3Y4ecCrk6UgqDLl6Tpp72v Uvv1vlvxUZmfg8nw8sz5DLmFKAAVgws7z X-Gm-Gg: ASbGnctItnObT0DcIcMDVug30IjECRRbJf1sasMv6gPWleRxYNcMl9xbGQnC6A9Jbmu DAWOvEA5+916sfBjdJMZ1dJlgWIB6f6vTW8Y= X-Google-Smtp-Source: AGHT+IHNujdTRH9brPjn0CmQwlUncPtoXjMXPcERzxwUEaJigd8gM2XvUJYxnuLgk/d0s0JY1VED7r6lcw1sZhzpcHs= X-Received: by 2002:a05:651c:a0b:b0:302:1861:6df4 with SMTP id 38308e7fff4ca-302545b95a2mr46054921fa.35.1734409918208; Mon, 16 Dec 2024 20:31:58 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Kirill Reshke Date: Tue, 17 Dec 2024 09:31:46 +0500 Message-ID: Subject: Re: on_error table, saving error info to a table To: Nishant Sharma Cc: jian he , PostgreSQL Hackers Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Mon, 16 Dec 2024 at 16:50, Nishant Sharma wrote: > Also, I think Andrew's suggestion can resolve the concern me and Krill > had on forcing users to create tables with correct column names and > numbers. Also, will make error table checking simpler. No need for the > above kind of checks. +1 on that. -- Best regards, Kirill Reshke