Re: Question on Table creation

*"1)In this situation , do we have to drop the "Schema_Owner" and recreate it with all small letters? And then create the schema with small letters again?"* As per above question goes, I believe OP is not required to drop and recreate but has to just Rename the user something as below and that

Re: User pooler error: unsupported startup parameter: extra_float_digits

Thank you very much ! On Tue, Feb 20, 2024 at 9:50 AM Greg Sabino Mullane wrote: > Add this to your pgbouncer config file: > > ignore_startup_parameters = extra_float_digits > > A web search of your subject line finds this solution quite easily. > Providing more details would also be a good

Re: Question on Table creation

On 2/20/24 13:19, sud wrote: Hi, We are newly creating tables in postgres 15.4 version and we got the DDL auto generated from one of the tools and they look something like below. (note- I have modified the exact names to some dummy names.) These are all failing because the schema which

Re: Question on Table creation

sud writes: > We are newly creating tables in postgres 15.4 version and we got the DDL > auto generated from one of the tools and they look something like below. > (note- I have modified the exact names to some dummy names.) These are all > failing because the schema which already exists in the

Question on Table creation

Hi, We are newly creating tables in postgres 15.4 version and we got the DDL auto generated from one of the tools and they look something like below. (note- I have modified the exact names to some dummy names.) These are all failing because the schema which already exists in the database having

Re: Partitioning options

On Sun, Feb 18, 2024 at 5:20 PM Alec Lazarescu wrote: > "Would probably look at a nested partitioning" > > I'm not the original poster, but I have a schema with nested > (composite) partitions and I do run into some significant > inefficiencies compared to flat partitions in various schema

Re: Mat Views and Conflicts

On 2/20/24 05:25, Zahir Lalani wrote: -From: David G. Johnston -Sent: Tuesday, February 20, 2024 1:20 PM -To: Zahir Lalani -Cc: Adrian Klaver ; pgsql-general@lists.postgresql.org -Subject: Re: Mat Views and Conflicts - - -On Tuesday, February 20, 2024, Zahir Lalani

Re: Mat Views and Conflicts

On 2/20/24 04:20, Zahir Lalani wrote: 1) When you say '... ran the underlying query ...' are you referring to: REFRESH MATERIALIZED VIEW https://www.postgresql.org/docs/current/sql-refreshmaterializedview.html 2) What is the complete error message from the Postgres log? Have I got it

Re: User pooler error: unsupported startup parameter: extra_float_digits

Add this to your pgbouncer config file: ignore_startup_parameters = extra_float_digits A web search of your subject line finds this solution quite easily. Providing more details would also be a good idea for future emails. Cheers, Greg

RE: Mat Views and Conflicts

-From: David G. Johnston -Sent: Tuesday, February 20, 2024 1:20 PM -To: Zahir Lalani -Cc: Adrian Klaver ; pgsql-general@lists.postgresql.org -Subject: Re: Mat Views and Conflicts - - -On Tuesday, February 20, 2024, Zahir Lalani wrote: - -This suggests that

Re: Mat Views and Conflicts

On Tuesday, February 20, 2024, Zahir Lalani wrote: > > > This suggests that not all the MV data is cached and it still queries the > source tables in some way? > > No. That isn’t how MV work. If you include an MV relation in your query from clause there is no reference or knowledge as to the

RE: array_to_json/array_agg question

On 2024-02-20 10:48 +0100, Laura Smith wrote: > Before I go down the road of taking care of this in the front-end > through iterations, I thought I would ask the pgsql if there was a > clever query I could do on postgres that would take care of it for me > instead. > > In essence, I would like

Re: array_to_json/array_agg question

> You almost got the subrecord ("value_1" and "value_2") right. You need > to use json_build_object() (or even the new json_object() function added > in pg16) instead of row_to_json() to just include "value_1" and > "value_2". Then GROUP BY "key" and aggregate the subrecords with > json_agg().

RE: Mat Views and Conflicts

> -Original Message- > From: Adrian Klaver > Sent: Monday, February 19, 2024 7:36 PM > To: Zahir Lalani ; pgsql- > gene...@lists.postgresql.org > Subject: Re: Mat Views and Conflicts > > On 2/19/24 09:52, Zahir Lalani wrote: > > Hi All > > > > My understanding and hope was that Mat Views

Re: array_to_json/array_agg question

On 2024-02-20 10:48 +0100, Laura Smith wrote: > Before I go down the road of taking care of this in the front-end > through iterations, I thought I would ask the pgsql if there was a > clever query I could do on postgres that would take care of it for me > instead. > > In essence, I would like to

array_to_json/array_agg question

Hi Before I go down the road of taking care of this in the front-end through iterations, I thought I would ask the pgsql if there was a clever query I could do on postgres that would take care of it for me instead. In essence, I would like to consolidate values from the same key as a json

Re: Identifying optimizer usage of indexed expressions

On Mon, 2024-02-19 at 23:08 +, Tim Palmer wrote: > I can identify indexes that are used directly during query execution using > pg_stat_user_indexes. However, it is possible that the optimizer might be > using the statistics on the indexed expressions to guide query planning. > If that is the