Re: Using compression on TCP transfer

[Olivier Gautherot]

Hi Andrus,

Le sam. 4 avr. 2020 à 10:09, Andrus  a écrit :

> Hi!
>
> >> In case of varchar field values will appear in database sometimes with
> >> trailing spaces and sometimes without.
> >> This requires major application re-design which much is more expensive
> than
> >> continuing using char fields.
> >A simple BEFORE INSERT OR UPDATE trigger would take care of that.
>
> Changing char to varchar will break commands where trailing space is used
> in comparison.
>
> For example query
>
> create table test ( test char(10) );
> insert into test values ('test');
> select * from test where test ='test '; -- note trailing space
>
> does not return data anymore if your recommendation is used:
>
> create table test ( test varchar );
> insert into test values ('test');
> select * from test where test ='test '; -- note trailing space
>
> In production 'test ' is query parameter coming from application with
> possible trailing space(s).
>
> Adding trigger does not fix this.
> How to fix this without re-writing huge number of sql commands?
>

In the end, your question is more at application level than database
itself. The real question is: which one is correct? With or without
trailing space?

If you decide that it's without, you could apply a TRIM in a trigger on
each INSERT and UPDATE. Then, you could replace the table by a view of the
same name and implement the TRIM on SELECT there. This way, you don't have
to touch anything in the application.

Hope it helps
Olivier

>

psql show me the : and ask user input, when running one sql file

[arden liu]

I am using psql to run this sql file(
https://github.com/Arelle/Arelle/blob/master/arelle/plugin/xbrlDB/sql/public/xbrlPublicPostgresDB.ddl
)
here is my command:
/usr/bin/psql postgresql://db_user:dbpassword@localhost:5432/my_db -f
/tmp/xbrlPublicPostgresDB.ddl
I do not know why it show me the : , which is asking me to input something.
Can someone help me?
Thanks.
Arden

Re: psql show me the : and ask user input, when running one sql file

[David G. Johnston]

On Sun, Apr 5, 2020 at 5:50 AM arden liu  wrote:

> I am using psql to run this sql file(
> https://github.com/Arelle/Arelle/blob/master/arelle/plugin/xbrlDB/sql/public/xbrlPublicPostgresDB.ddl
> )
> here is my command:
> /usr/bin/psql postgresql://db_user:dbpassword@localhost:5432/my_db -f
> /tmp/xbrlPublicPostgresDB.ddl
> I do not know why it show me the : , which is asking me to input
> something.
> Can someone help me?
>

If you can manually execute incremental portions of the file until the
final statement introduces the problem I'll be happy to try and explain
what may be wrong with that statement or portion of the file.

Removing stuff instead of just commenting it out is recommended.

David J.

Re: psql show me the : and ask user input, when running one sql file

[Rob Sargent]

> On Apr 5, 2020, at 8:24 AM, David G. Johnston  
> wrote:
> 
> 
>> On Sun, Apr 5, 2020 at 5:50 AM arden liu  wrote:
>> I am using psql to run this sql 
>> file(https://github.com/Arelle/Arelle/blob/master/arelle/plugin/xbrlDB/sql/public/xbrlPublicPostgresDB.ddl)
>> here is my command:
>> /usr/bin/psql postgresql://db_user:dbpassword@localhost:5432/my_db -f 
>> /tmp/xbrlPublicPostgresDB.ddl
>> I do not know why it show me the : , which is asking me to input something. 
>> Can someone help me?
> 
> If you can manually execute incremental portions of the file until the final 
> statement introduces the problem I'll be happy to try and explain what may be 
> wrong with that statement or portion of the file.
> 
> Removing stuff instead of just commenting it out is recommended.
> 
> David J.
> 

Or change your semi-colons into \p\g and perhaps we’ll see the lasting thing 
run. 

Re: psql show me the : and ask user input, when running one sql file

[Tim Clarke]

Arden

Your first argument is a JDBC connection string (see here
https://jdbc.postgresql.org/documentation/80/connect.html). To provide
the details when using the command line psql command, use the -h, -p and
-U parameters (https://www.postgresql.org/docs/12/app-psql.html)

Tim Clarke
IT Director
Direct: +44 (0)1376 504510 | Mobile: +44 (0)7887 563420

On 05/04/2020 13:50, arden liu wrote:

I am using psql to run this sql
file(https://github.com/Arelle/Arelle/blob/master/arelle/plugin/xbrlDB/sql/public/xbrlPublicPostgresDB.ddl)
here is my command:
/usr/bin/psql postgresql://db_user:dbpassword@localhost:5432/my_db -f
/tmp/xbrlPublicPostgresDB.ddl
I do not know why it show me the : , which is asking me to input
something.
Can someone help me?
Thanks.
Arden



Telephone: Witham: +44(0)1376 503500 | London: +44 (0)20 3009 0853 | Frankfurt: 
+49 (0)69 7191 6000 | Hong Kong: +852 5803 1687 | Toronto: +1 647 503 2848
Web: https://www.manifest.co.uk/



Minerva Analytics Ltd - A Solactive Company
9 Freebournes Court | Newland Street | Witham | Essex | CM8 2BL | United Kingdom



Copyright: This e-mail may contain confidential or legally privileged information. If 
you are not the named addressee you must not use or disclose such information, 
instead please report it to ad...@minerva.info
Legal: Minerva Analytics is the trading name of: Minerva Analytics Ltd: Registered 
in England Number 11260966 & The Manifest Voting Agency Ltd: Registered in 
England Number 2920820 Registered Office at above address. Please Click Here 
https://www.manifest.co.uk/legal/ for further information.

Re: psql show me the : and ask user input, when running one sql file

[David G. Johnston]

On Sun, Apr 5, 2020 at 7:47 AM Tim Clarke  wrote:

> Your first argument is a JDBC connection string (see here
> https://jdbc.postgresql.org/documentation/80/connect.html). To provide
> the details when using the command line psql command, use the -h, -p and
> -U parameters (https://www.postgresql.org/docs/12/app-psql.html)
>
>
libpq understands URI connection strings:

https://www.postgresql.org/docs/12/libpq-connect.html#LIBPQ-CONNSTRING

David J.

Re: Using compression on TCP transfer

[Andrus]

Hi!
Thank you.

>If you decide that it's without, you could apply a TRIM in a trigger on each 
>INSERT and UPDATE. Then, you could replace the table by a view of the same 
>name >and implement the TRIM on SELECT there. This way, you don't have to 
>touch anything in the application.

How you provide sample code how to create view or othe method test so that my 
select statement returns data.

Currently select in code

create table test ( test varchar );
insert into test values ('test');
select * from test where test ='test '; -- note trailing space


does not return data.

Andrus.

Re: psql show me the : and ask user input, when running one sql file

[Adrian Klaver]

On 4/5/20 5:50 AM, arden liu wrote:
I am using psql to run this sql 
file(https://github.com/Arelle/Arelle/blob/master/arelle/plugin/xbrlDB/sql/public/xbrlPublicPostgresDB.ddl)

here is my command:
/usr/bin/psql postgresql://db_user:dbpassword@localhost:5432/my_db -f 
/tmp/xbrlPublicPostgresDB.ddl

I do not know why it show me the : , which is asking me to input something.


You are going to need to provide more context about where the : is 
showing up.


You will need to show  the actual complete line that shows up?

Also it would be helpful to see anything directly preceding the line.

I would also suggest looking at the Postgres log(assuming you have 
log_statement set to at least mod) to see where in the sequence of 
commands you run into the 'input'.




Can someone help me?
Thanks.
Arden



--
Adrian Klaver
adrian.kla...@aklaver.com

Re: psql show me the : and ask user input, when running one sql file

[Adrian Klaver]

On 4/5/20 5:50 AM, arden liu wrote:
I am using psql to run this sql 
file(https://github.com/Arelle/Arelle/blob/master/arelle/plugin/xbrlDB/sql/public/xbrlPublicPostgresDB.ddl)

here is my command:
/usr/bin/psql postgresql://db_user:dbpassword@localhost:5432/my_db -f 
/tmp/xbrlPublicPostgresDB.ddl

I do not know why it show me the : , which is asking me to input something.
Can someone help me?


Well I ran the file(basically a modified dump file) and what I found is it:

1) Hung on:

 INSERT INTO industry (industry_id, industry_classification, 
industry_code, industry_description, depth, parent_id) VALUES

...
RETURNING industry_id;

INSERT 0 4333

and

INSERT INTO industry_level (industry_level_id, industry_classification, 
ancestor_id, ancestor_code, ancestor_depth, descendant_id, 
descendant_code, descendant_depth) VALUES

...
RETURNING industry_level_id;

INSERT 0 9326

2) It did not hang on:

INSERT INTO industry_structure (industry_structure_id, 
industry_classification, depth, level_name) VALUES

...
RETURNING industry_structure_id;

INSERT 0 13

3) For the hung cases all the INSERTS completed, I just needed to hit 
any key to get the next INSERT statement to kick off.


4) I don't see anything wrong the statements, so I am wondering if it is 
a shell issue?





Thanks.
Arden



--
Adrian Klaver
adrian.kla...@aklaver.com

Re: psql show me the : and ask user input, when running one sql file

[Adrian Klaver]

On 4/5/20 9:46 AM, Adrian Klaver wrote:

On 4/5/20 5:50 AM, arden liu wrote:
I am using psql to run this sql 
file(https://github.com/Arelle/Arelle/blob/master/arelle/plugin/xbrlDB/sql/public/xbrlPublicPostgresDB.ddl) 


here is my command:
/usr/bin/psql postgresql://db_user:dbpassword@localhost:5432/my_db -f 
/tmp/xbrlPublicPostgresDB.ddl
I do not know why it show me the : , which is asking me to input 
something.

Can someone help me?


Well I ran the file(basically a modified dump file) and what I found is it:

1) Hung on:

  INSERT INTO industry (industry_id, industry_classification, 
industry_code, industry_description, depth, parent_id) VALUES

...
RETURNING industry_id;

INSERT 0 4333

and

INSERT INTO industry_level (industry_level_id, industry_classification, 
ancestor_id, ancestor_code, ancestor_depth, descendant_id, 
descendant_code, descendant_depth) VALUES

...
RETURNING industry_level_id;

INSERT 0 9326

2) It did not hang on:

INSERT INTO industry_structure (industry_structure_id, 
industry_classification, depth, level_name) VALUES

...
RETURNING industry_structure_id;

INSERT 0 13

3) For the hung cases all the INSERTS completed, I just needed to hit 
any key to get the next INSERT statement to kick off.


4) I don't see anything wrong the statements, so I am wondering if it is 
a shell issue?



Hit Enter too soon.

5) All the other objects in the file where created.






Thanks.
Arden






--
Adrian Klaver
adrian.kla...@aklaver.com

Re: psql show me the : and ask user input, when running one sql file

[Adrian Klaver]

On 4/5/20 9:46 AM, Adrian Klaver wrote:

On 4/5/20 5:50 AM, arden liu wrote:


4) I don't see anything wrong the statements, so I am wondering if it is 
a shell issue?


Seems to be. I removed the RETURNING *_id from the INSERT statements and 
the file ran without interruption:


...
CREATE TABLE
ALTER TABLE
INSERT 0 4333
INSERT 0 9326
INSERT 0 13
ALTER TABLE
ALTER TABLE
...






Thanks.
Arden






--
Adrian Klaver
adrian.kla...@aklaver.com

Re: psql show me the : and ask user input, when running one sql file

[arden liu]

When I run any smaller SQL, psql does not ask any keyboard Input. I don't
know what causes this input

On Sun., Apr. 5, 2020, 12:46 p.m. Adrian Klaver, 
wrote:

> On 4/5/20 5:50 AM, arden liu wrote:
> > I am using psql to run this sql
> > file(
> https://github.com/Arelle/Arelle/blob/master/arelle/plugin/xbrlDB/sql/public/xbrlPublicPostgresDB.ddl
> )
> > here is my command:
> > /usr/bin/psql postgresql://db_user:dbpassword@localhost:5432/my_db -f
> > /tmp/xbrlPublicPostgresDB.ddl
> > I do not know why it show me the : , which is asking me to input
> something.
> > Can someone help me?
>
> Well I ran the file(basically a modified dump file) and what I found is it:
>
> 1) Hung on:
>
>   INSERT INTO industry (industry_id, industry_classification,
> industry_code, industry_description, depth, parent_id) VALUES
> ...
> RETURNING industry_id;
>
> INSERT 0 4333
>
> and
>
> INSERT INTO industry_level (industry_level_id, industry_classification,
> ancestor_id, ancestor_code, ancestor_depth, descendant_id,
> descendant_code, descendant_depth) VALUES
> ...
> RETURNING industry_level_id;
>
> INSERT 0 9326
>
> 2) It did not hang on:
>
> INSERT INTO industry_structure (industry_structure_id,
> industry_classification, depth, level_name) VALUES
> ...
> RETURNING industry_structure_id;
>
> INSERT 0 13
>
> 3) For the hung cases all the INSERTS completed, I just needed to hit
> any key to get the next INSERT statement to kick off.
>
> 4) I don't see anything wrong the statements, so I am wondering if it is
> a shell issue?
>
>
>
> > Thanks.
> > Arden
>
>
> --
> Adrian Klaver
> adrian.kla...@aklaver.com
>

Re: psql show me the : and ask user input, when running one sql file

[arden liu]

Hi Adrian,
When I use the following java to run the same command, which does not ask
me any input.  Maybe bash and java launch another process differently.
-
String command = "/usr/bin/psql postgresql://" +userName + ":" + password
+"@"+ host + ":" + port + "/xbrlam -f /tmp/xbrlPublicPostgresDB.ddl";
try {
Process process = Runtime.getRuntime().exec(command);
StreamGobbler streamGobbler = new StreamGobbler(process.getInputStream(),
System.out::println);
Executors.newSingleThreadExecutor().submit(streamGobbler);

int exitValue = process.waitFor();
if (exitValue == 0) {
System.out.println("XBRL-US db is ready.");
} else {
throw new RuntimeException("XBRL-US db wrong");
}
} catch (Exception e) {
throw new RuntimeException(e);
}

On Sun., Apr. 5, 2020, 12:47 p.m. Adrian Klaver, 
wrote:

> On 4/5/20 9:46 AM, Adrian Klaver wrote:
> > On 4/5/20 5:50 AM, arden liu wrote:
> >> I am using psql to run this sql
> >> file(
> https://github.com/Arelle/Arelle/blob/master/arelle/plugin/xbrlDB/sql/public/xbrlPublicPostgresDB.ddl)
>
> >>
> >> here is my command:
> >> /usr/bin/psql postgresql://db_user:dbpassword@localhost:5432/my_db -f
> >> /tmp/xbrlPublicPostgresDB.ddl
> >> I do not know why it show me the : , which is asking me to input
> >> something.
> >> Can someone help me?
> >
> > Well I ran the file(basically a modified dump file) and what I found is
> it:
> >
> > 1) Hung on:
> >
> >   INSERT INTO industry (industry_id, industry_classification,
> > industry_code, industry_description, depth, parent_id) VALUES
> > ...
> > RETURNING industry_id;
> >
> > INSERT 0 4333
> >
> > and
> >
> > INSERT INTO industry_level (industry_level_id, industry_classification,
> > ancestor_id, ancestor_code, ancestor_depth, descendant_id,
> > descendant_code, descendant_depth) VALUES
> > ...
> > RETURNING industry_level_id;
> >
> > INSERT 0 9326
> >
> > 2) It did not hang on:
> >
> > INSERT INTO industry_structure (industry_structure_id,
> > industry_classification, depth, level_name) VALUES
> > ...
> > RETURNING industry_structure_id;
> >
> > INSERT 0 13
> >
> > 3) For the hung cases all the INSERTS completed, I just needed to hit
> > any key to get the next INSERT statement to kick off.
> >
> > 4) I don't see anything wrong the statements, so I am wondering if it is
> > a shell issue?
>
>
> Hit Enter too soon.
>
> 5) All the other objects in the file where created.
>
> >
> >
> >
> >> Thanks.
> >> Arden
> >
> >
>
>
> --
> Adrian Klaver
> adrian.kla...@aklaver.com
>

Re: psql show me the : and ask user input, when running one sql file

[arden liu]

Does that RETURNING need any user input?

On Sun., Apr. 5, 2020, 1:10 p.m. Adrian Klaver, 
wrote:

> On 4/5/20 9:46 AM, Adrian Klaver wrote:
> > On 4/5/20 5:50 AM, arden liu wrote:
>
> > 4) I don't see anything wrong the statements, so I am wondering if it is
> > a shell issue?
>
> Seems to be. I removed the RETURNING *_id from the INSERT statements and
> the file ran without interruption:
>
> ...
> CREATE TABLE
> ALTER TABLE
> INSERT 0 4333
> INSERT 0 9326
> INSERT 0 13
> ALTER TABLE
> ALTER TABLE
> ...
>
> >
> >
> >
> >> Thanks.
> >> Arden
> >
> >
>
>
> --
> Adrian Klaver
> adrian.kla...@aklaver.com
>

Re: psql show me the : and ask user input, when running one sql file

[Adrian Klaver]

On 4/5/20 10:51 AM, arden liu wrote:

Does that RETURNING need any user input?


No. I just think actually returning those thousands of values is 
stalling the shell. It also not really necessary for the loading as 
'INSERT 0 4333' shows you what you need to know. Unless you have super 
vision and recall you are not going to track those values anyway. You 
can verify in the table itself.


I would see if you could get the project to output the file using COPY 
to load the tables instead of INSERT anyway. The file is pretty much 
Postgres specific anyway as it doing things like:


1) DROP SCHEMA public CASCADE; create SCHEMA public;

SET statement_timeout = 0;
SET client_encoding = 'UTF8';
-- HF - must have conforming strings on for Postgres interface to work, 
as it will include Windows paths sometimes

SET standard_conforming_strings = on;
SET check_function_bodies = false;
SET client_min_messages = warning;
SET escape_string_warning = off;

SET search_path = public, pg_catalog;

2) ALTER TYPE public.ancestry OWNER TO postgres;



On Sun., Apr. 5, 2020, 1:10 p.m. Adrian Klaver, 
mailto:adrian.kla...@aklaver.com>> wrote:


On 4/5/20 9:46 AM, Adrian Klaver wrote:
 > On 4/5/20 5:50 AM, arden liu wrote:

 > 4) I don't see anything wrong the statements, so I am wondering
if it is
 > a shell issue?

Seems to be. I removed the RETURNING *_id from the INSERT statements
and
the file ran without interruption:

...
CREATE TABLE
ALTER TABLE
INSERT 0 4333
INSERT 0 9326
INSERT 0 13
ALTER TABLE
ALTER TABLE
...

 >
 >
 >
 >> Thanks.
 >> Arden
 >
 >


-- 
Adrian Klaver

adrian.kla...@aklaver.com 




--
Adrian Klaver
adrian.kla...@aklaver.com

Re: psql show me the : and ask user input, when running one sql file

[arden liu]

Hi Adrian,
I also consider it's related to Shell . Because when I run it from Java , I
don't have this input request.

Let me check some configuration of bash and try again.

Thanks  a lot.
Arden

On Sun., Apr. 5, 2020, 2:09 p.m. Adrian Klaver, 
wrote:

> On 4/5/20 10:51 AM, arden liu wrote:
> > Does that RETURNING need any user input?
>
> No. I just think actually returning those thousands of values is
> stalling the shell. It also not really necessary for the loading as
> 'INSERT 0 4333' shows you what you need to know. Unless you have super
> vision and recall you are not going to track those values anyway. You
> can verify in the table itself.
>
> I would see if you could get the project to output the file using COPY
> to load the tables instead of INSERT anyway. The file is pretty much
> Postgres specific anyway as it doing things like:
>
> 1) DROP SCHEMA public CASCADE; create SCHEMA public;
>
> SET statement_timeout = 0;
> SET client_encoding = 'UTF8';
> -- HF - must have conforming strings on for Postgres interface to work,
> as it will include Windows paths sometimes
> SET standard_conforming_strings = on;
> SET check_function_bodies = false;
> SET client_min_messages = warning;
> SET escape_string_warning = off;
>
> SET search_path = public, pg_catalog;
>
> 2) ALTER TYPE public.ancestry OWNER TO postgres;
>
> >
> > On Sun., Apr. 5, 2020, 1:10 p.m. Adrian Klaver,
> > mailto:adrian.kla...@aklaver.com>> wrote:
> >
> > On 4/5/20 9:46 AM, Adrian Klaver wrote:
> >  > On 4/5/20 5:50 AM, arden liu wrote:
> >
> >  > 4) I don't see anything wrong the statements, so I am wondering
> > if it is
> >  > a shell issue?
> >
> > Seems to be. I removed the RETURNING *_id from the INSERT statements
> > and
> > the file ran without interruption:
> >
> > ...
> > CREATE TABLE
> > ALTER TABLE
> > INSERT 0 4333
> > INSERT 0 9326
> > INSERT 0 13
> > ALTER TABLE
> > ALTER TABLE
> > ...
> >
> >  >
> >  >
> >  >
> >  >> Thanks.
> >  >> Arden
> >  >
> >  >
> >
> >
> > --
> > Adrian Klaver
> > adrian.kla...@aklaver.com 
> >
>
>
> --
> Adrian Klaver
> adrian.kla...@aklaver.com
>

Re: psql show me the : and ask user input, when running one sql file

[Daniel Verite]

Adrian Klaver wrote:

> On 4/5/20 9:46 AM, Adrian Klaver wrote:
> > On 4/5/20 5:50 AM, arden liu wrote:
> 
> > 4) I don't see anything wrong the statements, so I am wondering if it is 
> > a shell issue?
> 
> Seems to be. I removed the RETURNING *_id from the INSERT statements and 
> the file ran without interruption:

Presumably these results are being displayer with a pager, and it's
the pager that is asking for keyboard input.
You may add -P pager=off to psql options to suppress this,
or remove permanently the RETURNING clauses that seem pointless
in that context.


Best regards,
-- 
Daniel Vérité
PostgreSQL-powered mailer: http://www.manitou-mail.org
Twitter: @DanielVerite

Re: psql show me the : and ask user input, when running one sql file

[arden liu]

Hi Daniel,
"-P pager=off" works I think you found the root cause.

Thanks for your help.
Arden

On Sun, Apr 5, 2020 at 2:32 PM Daniel Verite 
wrote:

> Adrian Klaver wrote:
>
> > On 4/5/20 9:46 AM, Adrian Klaver wrote:
> > > On 4/5/20 5:50 AM, arden liu wrote:
> >
> > > 4) I don't see anything wrong the statements, so I am wondering if it
> is
> > > a shell issue?
> >
> > Seems to be. I removed the RETURNING *_id from the INSERT statements and
> > the file ran without interruption:
>
> Presumably these results are being displayer with a pager, and it's
> the pager that is asking for keyboard input.
> You may add -P pager=off to psql options to suppress this,
> or remove permanently the RETURNING clauses that seem pointless
> in that context.
>
>
> Best regards,
> --
> Daniel Vérité
> PostgreSQL-powered mailer: http://www.manitou-mail.org
> Twitter: @DanielVerite
>

Server with hot standby slave wont start after vacuum

[Andrus]

Hi!

Streaming asynchronous binary replication is used with hot standby slave.

To recover disk space

vacuumdb --all --full --skip-locked

is executed in every night is master.

During this vacuumdb stops with error

vacuumdb: error: vacuuming of table "myschema.mytable" in database "mydb" failed: PANIC:  could not write to file 
"pg_wal/xlogtemp.24729": No space left on device

server closed the connection unexpectedly
   This probably means the server terminated abnormally
   before or while processing the request.

And master wont start anymore:

LOG:  server process (PID 24729) was terminated by signal 6: Aborted
DETAIL:  Failed process was running: VACUUM (SKIP_LOCKED, FULL) firma39.rid;
LOG:  terminating any other active server processes
WARNING:  terminating connection because of crash of another server process
DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server 
process exited abnormally and possibly corrupted shared memory.

HINT:  In a moment you should be able to reconnect to the database and repeat 
your command.
...
LOG:  all server processes terminated; reinitializing
LOG:  database system was interrupted; last known up at 2020-04-06 01:14:10 EEST
LOG:  database system was not properly shut down; automatic recovery in progress
LOG:  redo starts at 2A0/C414BA68
FATAL:  could not extend file "global/58294678": wrote only 4096 of 8192 bytes 
at block 1728
HINT:  Check free disk space.
CONTEXT:  WAL redo at 2A0/D661D4B0 for XLOG/FPI:
LOG:  startup process (PID 24732) exited with exit code 1
LOG:  aborting startup due to startup process failure
LOG:  database system is shut down

pg_wal contains 2005 files with total size 32 GB and there is no free disk 
space.

hot standby server is connected over 20 Mbit internet.

Maybe vacuum full causes creation of creates huge number files in pg_wal which 
cannot transferred fast over 20Mbit internet.

How to fix this so that master continues to work?
Mabe it is possible to disable creation of wal files by vacuum.

Postgres 12 in Debian is used.

Andrus.