Re: Tablespace column value null on select * from pg_tables

On 7/28/19 1:24 PM, Peter J. Holzer wrote: On 2019-07-16 19:20:24 +, Alex Williams wrote: 1. postgres=# ALTER DATABASE mydatabase SET TABLESPACE pg_default; ERROR: some relations of database "mydatabase" are already in tablespace "pg_default" HINT: You must move them back to the databas

Re: Tablespace column value null on select * from pg_tables

"Peter J. Holzer" writes: > On 2019-07-16 19:20:24 +, Alex Williams wrote: >> 1. postgres=# ALTER DATABASE mydatabase SET TABLESPACE pg_default; >> ERROR: some relations of database "mydatabase" are already in tablespace >> "pg_default" >> HINT: You must move them back to the database's def

Re: Tablespace column value null on select * from pg_tables

On 2019-07-16 19:20:24 +, Alex Williams wrote: > 1. postgres=# ALTER DATABASE mydatabase SET TABLESPACE pg_default; > > ERROR: some relations of database "mydatabase" are already in tablespace > "pg_default" > > HINT: You must move them back to the database's default tablespace before > u

Re: Why does backend send buffer size hardcoded at 8KB?

On 2019-07-27 19:10:22 -0400, Tom Lane wrote: > Andres Freund writes: > > On 2019-07-27 18:34:50 -0400, Tom Lane wrote: > >> Yeah. The existing commentary about that is basically justifying 8K > >> as being large enough to avoid performance issues; if somebody can > >> show that that's not true,

Re: logging "raise" to file

Thank Georg, regards walter > the red part writes your "raise notice" to your log > > psql (+your connection string) -f /path/to/file.sql *> > /path/to/log/xxx.log 2>&1* > > -- My projects: Admin Boundaries of the World Missing Boundaries

Re: logging "raise" to file

Hi, Am 28.07.2019 um 12:32 schrieb wambac...@posteo.de: Hi, is there a way to log output from "raise ..." to a local file? \o file does not work (for me). regards walter the red part writes your "raise notice" to your log psql (+your connection string) -f /path/to/file.sql *> /path/to/

Re: logging "raise" to file

Hi, Le dim. 28 juil. 2019 à 12:32, a écrit : > Hi, > > is there a way to log output from "raise ..." to a local file? \o file > does not work (for me). > No, RAISE messages can only go to log files. You would need to call a function that could write to a file (though without calling RAISE). -

logging "raise" to file

Hi, is there a way to log output from "raise ..." to a local file? \o file does not work (for me). regards walter -- My projects: Admin Boundaries of the World Missing Boundaries

RE: Hardware for writing/updating 12,000,000 rows per hour

HI Arya, Probably the easiest solution is to use cloud computing with dedicated network. Good luck. From: Neil Sent: 2019 July 28 01:33 To: Arya F Cc: pgsql-general@lists.postgresql.org; farjad.farid ; Alvaro Herrera ; Tom Lane ; Ron Subject: Re: Hardware for writing/updating 12,000,000

Re: Too slow to create new schema and their tables, functions, triggers.

On Fri, Jul 26, 2019 at 9:21 PM PegoraroF10 wrote: > So, is it better to configure autovacuum properly to these tables or should > I run vacuum periodically ? > Obviously I´ll check our script too. > My guess would be that either you have disabled autovacuum on such tables (I don't know if that i