Date: Fri, 18 Apr 2025 11:20:13 +0000 (UTC)
From: "sivapostgres@yahoo.com" <sivapostgres@yahoo.com>
Reply-To: "sivapostgres@yahoo.com" <sivapostgres@yahoo.com>
To: Pgsql-general <pgsql-general@postgresql.org>, 
	Laurenz Albe <laurenz.albe@cybertec.at>
Message-ID: <1365122733.3205645.1744975213857@mail.yahoo.com>
In-Reply-To: <24bb716bbdb6dbb8ac02c501db26731a101d21d3.camel@cybertec.at>
References: <1385521371.3160626.1744955370756.ref@mail.yahoo.com> <1385521371.3160626.1744955370756@mail.yahoo.com> <02e2740edf821e2ce84773c83065b45e9be890cc.camel@cybertec.at> <1852089030.3173833.1744961512201@mail.yahoo.com> <24bb716bbdb6dbb8ac02c501db26731a101d21d3.camel@cybertec.at>
Subject: Re:  Error while updating a table
MIME-Version: 1.0
Content-Type: multipart/alternative; 
	boundary="----=_Part_3205644_1903717107.1744975213856"
Content-Length: 2754
Archived-At: <https://www.postgresql.org/message-id/1365122733.3205645.1744975213857%40mail.yahoo.com>
Precedence: bulk

------=_Part_3205644_1903717107.1744975213856
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

 If the query caused an error ....
Does it mean that other reasons might also be there?
Nevertheless, I'll check the log file to find the query...
Happiness Always
BKR Sivaprakash
    On Friday 18 April, 2025 at 03:53:06 pm IST, Laurenz Albe <laurenz.albe@cybertec.at> wrote:  
 
 On Fri, 2025-04-18 at 07:31 +0000, sivapostgres@yahoo.com wrote:
> For the second part, how to identify that culprit query?

If the query caused an error, and you left "log_min_messages" at the
default setting, the error and the statement that caused it should
be in the PostgreSQL log.

Yours,
Laurenz Albe


------=_Part_3205644_1903717107.1744975213856
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<html><head></head><body><div class="ydp21a80d4cyahoo-style-wrap" style="font-family:times new roman, new york, times, serif;font-size:16px;"><div></div>
        <div dir="ltr" data-setdir="false">If the query caused an error ....</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">Does it mean that other reasons might also be there?</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">Nevertheless, I'll check the log file to find the query...</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">Happiness Always<br>BKR Sivaprakash</div><div><br></div>
        
        </div><div id="yahoo_quoted_5203182650" class="yahoo_quoted">
            <div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
                
                <div>
                        On Friday 18 April, 2025 at 03:53:06 pm IST, Laurenz Albe &lt;laurenz.albe@cybertec.at&gt; wrote:
                    </div>
                    <div><br></div>
                    <div><br></div>
                
                
                <div><div dir="ltr">On Fri, 2025-04-18 at 07:31 +0000, <a shape="rect" ymailto="mailto:sivapostgres@yahoo.com" href="mailto:sivapostgres@yahoo.com">sivapostgres@yahoo.com</a> wrote:<br clear="none">&gt; For the second part, how to identify that culprit query?<br clear="none"><br clear="none">If the query caused an error, and you left "log_min_messages" at the<br clear="none">default setting, the error and the statement that caused it should<br clear="none">be in the PostgreSQL log.<div class="yqt6176991185" id="yqtfd28014"><br clear="none"><br clear="none">Yours,<br clear="none">Laurenz Albe<br clear="none"><br clear="none"><br clear="none"></div></div></div>
            </div>
        </div></body></html>
------=_Part_3205644_1903717107.1744975213856--