Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hnJt3-0004HV-4g for pgsql-sql@arkaria.postgresql.org; Tue, 16 Jul 2019 09:36:41 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hnJt1-00031m-Is for pgsql-sql@arkaria.postgresql.org; Tue, 16 Jul 2019 09:36:39 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hnJt1-00030Z-AV for pgsql-sql@lists.postgresql.org; Tue, 16 Jul 2019 09:36:39 +0000 Received: from lungold.riddles.org.uk ([82.68.208.19]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hnJsv-00006h-7w for pgsql-sql@lists.postgresql.org; Tue, 16 Jul 2019 09:36:38 +0000 Received: from [192.168.127.1] (port=40634 helo=caithnard.riddles.org.uk) by lungold.riddles.org.uk with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.88 (FreeBSD)) (envelope-from ) id 1hnJst-0000Qs-T2; Tue, 16 Jul 2019 09:36:31 +0000 Received: from [127.0.0.1] (port=57545 helo=caithnard.riddles.org.uk) by caithnard.riddles.org.uk with esmtp (Exim 4.89 (FreeBSD)) (envelope-from ) id 1hnJst-0000Mz-8R; Tue, 16 Jul 2019 09:36:31 +0000 From: Andrew Gierth To: Karen Goh Cc: Subject: Re: Fw: how to resolve org.postgresql.util.PSQLException: ERROR: operator does not exist: text = integer? In-Reply-To: <1919398337.1106688.1563269115584@mail.yahoo.com> (Karen Goh's message of "Tue, 16 Jul 2019 09:25:15 +0000 (UTC)") Message-ID: <87k1ci1g9u.fsf@news-spur.riddles.org.uk> References: <110414461.528890.1563075361778@mail.yahoo.com> <1846547624.530883.1563075598322@mail.yahoo.com> <40544440.741577.1563178850210@mail.yahoo.com> <768811852.1032981.1563242356010@mail.yahoo.com> <774271584.1091322.1563257675315@mail.yahoo.com> <1984680550.1098414.1563257845450@mail.yahoo.com> <59735533.1068095.1563265280844@mail.yahoo.com> <87o91u1idu.fsf@news-spur.riddles.org.uk> <1919398337.1106688.1563269115584@mail.yahoo.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1 (berkeley-unix) Date: Tue, 16 Jul 2019 10:36:31 +0100 MIME-Version: 1.0 Content-Type: text/plain List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk >>>>> "Karen" == Karen Goh writes: >> You can get the statement from the server logs (by default, the >> statement text is logged alongside any error). Karen> Ok. Thanks. Just to confirm, I need log4j2 or SL4J to generate Karen> the log right? No. PostgreSQL writes its own logs. Most installs have some degree of logging enabled by default, though this does depend on what package was installed and how the server was started. In some cases you can figure out where the log files are from the following server settings (use the SHOW statement to display them): 1. If log_destination is "syslog", then whether a log file exists and where it is depends on the system's syslog.conf file. 2. If log_destination is "eventlog", then this is a Windows system, and log messages are in the Windows event log. 3. If log_destination is neither of the above, and logging_collector is enabled, then the log_directory setting shows where the log files are (if this is a relative path, it's relative to data_directory). 4. If log_destination is "stderr" and logging_collector is _disabled_, then the logs (if any) are written to wherever the startup script directed them. This depends on the OS and packaging. -- Andrew (irc:RhodiumToad)