Syntax

Hi All, What is the difference or use case for below syntaxes? do $$ declare d int; begin RAISE INFO 'Script started at %', CURRENT_TIMESTAMP; update employees set first_name = 'g' where employee_id = 1; get diagnostics d = row_count; raise info 'selected: % rows', d; RAISE INFO 'Script finished

Re: PostgreSQL 12 error unrecognized configuration parameter zbx_tmp.wal_json_res

Hi, Thanks for the reponse. What could the the potential consequenses of this error? Is it something that can be ignored until fix (hopefully) is provided, or are there critical functions now not working? Best regards, Arne H. ons. 6. des. 2023 kl. 17:21 skrev Adrian Klaver : > On 12/6/23 0

Re: Syntax

On Thu, Dec 7, 2023 at 3:01 AM arun chirappurath wrote: > Hi All, > > What is the difference or use case for below syntaxes? > > do $$ > declare d int; > begin > RAISE INFO 'Script started at %', CURRENT_TIMESTAMP; > update employees set first_name = 'g' where employee_id = 1; get > diagnostics d

Re: Trainning and Certification

Yes, a roadmap, training & certification who atest knowledge, skills in Postgresql technologies. Similar with training, certification for Oracle, Mysql. joi, 7 dec. 2023, 00:23 Daniel Gustafsson a scris: > > On 6 Dec 2023, at 16:30, roger popa wrote: > > > > Exist a top of this issue, for thi

Postgresql : pg_temp & pg_toast_temp

Hello Team I am seeing there are many schemas created, this is specially when enabled "CONCURRENTLY" option for refreshing materialized views through table trigger. pg_temp_1... pg_temp_30 pg_toast_temp_1... pg_toast_temp_30 If this is by design the temp schemas get created with the "CONCU

Re: Trainning and Certification

> On 7 Dec 2023, at 00:25, roger popa wrote: > > Yes, a roadmap, training & certification who atest knowledge, skills in > Postgresql technologies. > Similar with training, certification for Oracle, Mysql. The postgres project doesn't have a shared roadmap, each developer is free to pursue what

Re: Postgresql : pg_temp & pg_toast_temp

Vishwanath Kummera writes: >I am seeing there are many schemas created, this is specially when > enabled "CONCURRENTLY" option for refreshing materialized views through > table trigger. > pg_temp_1... pg_temp_30 > pg_toast_temp_1... pg_toast_temp_30 Yes, that's by design. There's a sepa

write a sql block which will commit if both updates are successful else it will have to be rolled back

Hi All, Can someone guide me to "write a sql block which will commit if both updates are successful else it will have to be rolled back"? would like to explicitly specify both commit and rollback in code.. I would like to turn off the autocommit then execute the query. Below is a just a starter

Re: write a sql block which will commit if both updates are successful else it will have to be rolled back

On Thursday, December 7, 2023, arun chirappurath wrote: > > > Can someone guide me to "write a sql block which will commit if both > updates are successful else it will have to be rolled back"? > would like to explicitly specify both commit and rollback in code.. > > I would like to turn off the

Invalid Parent Index Issue Will Not Resolve Despite Multiple Attempts To Fix

Hello all, We have been utilizing partitioned tables with indexes. We've recently had an issue where the parent table's index (id, date) became invalid (indisvalid=FALSE, indisready=FALSE in pg_index). For reference the parent table is partitioned on a date field within the table. In order to fin

Re: Invalid Parent Index Issue Will Not Resolve Despite Multiple Attempts To Fix

On Thu, 2023-12-07 at 16:38 -0600, Noel Jones wrote: > We have been utilizing partitioned tables with indexes. We've recently had an > issue > where the parent table's index (id, date) became invalid (indisvalid=FALSE, > indisready=FALSE in pg_index). For reference the parent table is partitioned

Disable script execution in server level when updating via grids

Hello All, Is there a way we can disable grid based updates from the clients in the server? suppose if someone accidentally commits an edit in dbeaver,server shall decline that incoming request. However requests from the query tool should run I have seen some options from the client side. Do