Re: verify checksums online

On Fri, 18 Apr 2025 17:32:19 -0400 Ron Johnson wrote: > On Fri, Apr 18, 2025 at 5:18 PM Jeremy Schneider > wrote: > > > i think there had been some mailing list discussions years ago? the > > pg_checksum utility in core still can't do an online check right? > > > > https://www.postgresql.org/d

Re: verify checksums online

On Fri, Apr 18, 2025 at 5:18 PM Jeremy Schneider wrote: > i should know the answer to this... but asking anyway > > i think there had been some mailing list discussions years ago? the > pg_checksum utility in core still can't do an online check right? > https://www.postgresql.org/docs/17/app-pgc

verify checksums online

i should know the answer to this... but asking anyway i think there had been some mailing list discussions years ago? the pg_checksum utility in core still can't do an online check right? looking around, i think that michael's pg_checksums_ext still seems to be available in debian repos, and it a

Re: Why is an error not thrown when the time exceeds the lock timeout for an ExclusiveLock on a transaction ?

display server side postgresql.conf varables from postgresql.conf Server-Side Timeout Configuration: 1. 1. statement_timeout

Re: Why is an error not thrown when the time exceeds the lock timeout for an ExclusiveLock on a transaction ?

"Mansky, Edmund J. (GSFC-671.0)[ADNET Affiliate]" writes: > I see in the log at that point : process 683860 still waiting for ShareLock > on transaction 492777941 after 1000.140 ms > while updating tuple > (1282991,25) in relation "sum_partn_alloc"

Why is an error not thrown when the time exceeds the lock timeout for an ExclusiveLock on a transaction ?

Hi Everyone, I have an SQL that updates a table in our database. The SQL in question is: UPDATE public.sum_partn_alloc AS T1 SET effective_date = to_char(CURRENT_TIMESTAMP + interval '6 days', 'MMDDHH24MI') FROM public.sum_main AS T2 WHERE T1.status != 8 AND (T1.effective_date = '0'

Re: Cannot turn track_counts on

On 4/17/25 15:25, Anton Shepelev wrote: Adrian Klaver to Anton Shepelev: Yet that is what we get for `pg_config --version' on the affected system. A nearly identical error message seems to come up while installing psycopg2 -- a Python library for Postgres, e.g.:

Re: Error while updating a table

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 wrote: On Fri, 2025-04-18 at 07:31 +, sivapost

Re: Error while updating a table

On Fri, 2025-04-18 at 07:31 +, sivapostg...@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, Laur

RE: Request for official clarification on SQL parameter parsing changes in PostgreSQL 15 and 16

Dear Tom, Laurenz, and Dominique, Thank you all very much for your helpful and detailed explanations. Your insights clarified the behavior change in PostgreSQL 15 perfectly, and I now have a clear understanding of the issue I was encountering. I really appreciate your time and support. Best re

Re: Cannot turn track_counts on

Adrian Klaver to Anton Shepelev: > >db=# show shared_preload_libraries; > > shared_preload_libraries > >--- > > online_analyze, plantuner > > Are you running PostgresPro? > > Both those modules are associated with it: > > https://postgrespro.com/docs/postgre

Re: Error while updating a table

Thanks Laurenz, Now I need to do 2 things. 1.  Correct my application to catch errors and do either Rollback or commit.    This part is running smoothly from all other computers, so far.  Nevertheless I'll check that for any missing catch.2.  Find the faulty entry and do rectify. For the second p