Re: Max size per relation for partitioned tables

2024-10-23 Thread David G. Johnston
On Wednesday, October 23, 2024, Reftel, Bengt Erik Magnus < magnus.ref...@skatteetaten.no> wrote: > > Appendix K of the documentation, https://www.postgresql.org/ > docs/current/limits.html , lists 32TB as the maximum size of a relation, > but it´s not clear to me whether “relation” in this context

Re: Backup

2024-10-23 Thread Andy Hartman
The images are part of the csv file... On Wed, Oct 23, 2024 at 3:47 PM Adrian Klaver wrote: > On 10/23/24 10:43, Andy Hartman wrote: > > I'm using the DB as a History repository... I'm pulling info from a > > Mssql db using a P/S script to a csv file then Import that to Postgres I > > only keep

Max size per relation for partitioned tables

2024-10-23 Thread Reftel, Bengt Erik Magnus
HI all, Appendix K of the documentation, https://www.postgresql.org/docs/current/limits.html , lists 32TB as the maximum size of a relation, but it´s not clear to me whether “relation” in this context for a partitioned table means the entire logical table, or just the individual physical table

Re: Backup

2024-10-23 Thread Adrian Klaver
On 10/23/24 10:43, Andy Hartman wrote: I'm using the DB as a History repository... I'm pulling info from a Mssql db using a P/S script to a csv file then Import that to Postgres I only keep 6 months live on the mssql db and roll everything else to Postgres Arch DB.   After I load this latest

Re: Backup

2024-10-23 Thread Andy Hartman
I'm using the DB as a History repository... I'm pulling info from a Mssql db using a P/S script to a csv file then Import that to Postgres I only keep 6 months live on the mssql db and roll everything else to Postgres Arch DB. After I load this latest month to Postgres I just need to backup, or

Re: Backup

2024-10-23 Thread Adrian Klaver
On 10/23/24 07:07, Andy Hartman wrote: I have been testing different backup methods suggested and wonder if I have all my files used to load the DB .. could that be considered a backup... obviously need to have schema backup in case of problem, but that seems to be easily re-created Thoughts?

Re: CONST :consttype relpartbound pg_class

2024-10-23 Thread Laurenz Albe
On Wed, 2024-10-23 at 17:07 +0300, Дмитрий wrote: > Can anyone tell me what this means «CONST :consttype 1184» или «CONST > :consttype 23» relpartbound pg_class? > I'm interested in what 1184 and 23 mean, and what other meanings they could > have? Where can I read about this? That looks like a p

CONST :consttype relpartbound pg_class

2024-10-23 Thread Дмитрий
Hello Evryone!   Can anyone tell me what this means  « CONST :consttype 1184 » или « CONST :consttype 23 » relpartbound   pg _ class ? I'm interested in what 1184 and 23 mean, and what other meanings they could have? Where can I read about this?   select pt.relpartbound from pg_class base_tb joi

Re: Backup

2024-10-23 Thread Andy Hartman
I have been testing different backup methods suggested and wonder if I have all my files used to load the DB .. could that be considered a backup... obviously need to have schema backup in case of problem, but that seems to be easily re-created Thoughts? On Fri, Oct 18, 2024 at 2:30 PM Adrian Kla

Re: CURRENTE_DATE

2024-10-23 Thread Ray O'Donnell
On 22/10/2024 12:31, Rossana Ocampos wrote: *Hello ,* I am new with PostgreSQL and I have a bug. I have created a function that has an input variable of type date , in case it does not receive value , it has to assume by default the current date. I have defined it as follows variable  DATE

Re: CURRENTE_DATE

2024-10-23 Thread Rich Shepard
On Tue, 22 Oct 2024, Rossana Ocampos wrote: ERROR: invalid input syntax for type date: "CURRENT_DATE" LINE 1: ...extsupplydate ('1085018'::bigint, '5278'::bigint, 'CURRENT_D... ^ ERROR: invalid input syntax for type date: "CURRENT_DATE" SQL status: 22007 Characters: 78 Rossana, Also, I sugges

Re: CURRENTE_DATE

2024-10-23 Thread Rich Shepard
On Tue, 22 Oct 2024, Rossana Ocampos wrote: I am new with PostgreSQL and I have a bug. I have created a function that has an input variable of type date , in case it does not receive value , it has to assume by default the current date. ERROR: invalid input syntax for type date: "CURRENT_DATE

CURRENTE_DATE

2024-10-23 Thread Rossana Ocampos
Hello , I am new with PostgreSQL and I have a bug. I have created a function that has an input variable of type date , in case it does not receive value , it has to assume by default the current date. I have defined it as follows variable DATE DEFAULT CURRENT_DATE, but I get the following error.