Ok, I replaced names of tables and columns and here is the query
explain (analyze, verbose, settings, format text) create table
dm.v_Table6_T_1 with (fillfactor = 100, parallel_workers = 20,
autovacuum_enabled = false, toast.autovacuum_enabled = false) as select
VHS.df_v_Table2_k
On 10/2/24 02:37, Pecsök Ján wrote:
Ok, I replaced names of tables and columns and here is the query
explain (analyze, verbose, settings, format text) create table
dm.v_Table6_T_1 with (fillfactor = 100, parallel_workers = 20,
autovacuum_enabled = false, toast.autovacuum_enabled = fal
On Wed, Oct 2, 2024, 11:17 Sam Kidman wrote:
>
> Unfortunately we use the latest version of the client tools (ie
> pg_dump and kin) but we run the same database server version as we use
> in production (12) and so now we're unable to import our database
> schema with the error below:
>
You are o
Hello
We're developing a rails application and part of our development
workflow involves dumping out the database schema using pg_dump, which
is restored whenever we drop and create our development database.
As of version 17 we now have SET transaction_timeout = 0 in the schema file.
Unfortunate
On 10/1/24 22:23, Sam Kidman wrote:
Hello
We're developing a rails application and part of our development
workflow involves dumping out the database schema using pg_dump, which
is restored whenever we drop and create our development database.
As of version 17 we now have SET transaction_timeou
> On 2 Oct 2024, at 07:23, Sam Kidman wrote:
> Are there any other solutions to this issue? It could be quite
> troublesome for us as we have a few different postgres server versions
> in use in different applications but we use the same set of client
> tools for all of them.
This is per design
