public inbox for [email protected]  

help / color / mirror / Atom feed

From: [email protected]
To: 'Erik Serrano' <[email protected]>
To: 'Samed YILDIRIM' <[email protected]>
Cc: 'Pgsql-admin' <[email protected]>
Cc: 'pgsql-admin' <[email protected]>
Subject: RE: PostgreSQL historical database
Date: Fri, 15 Nov 2024 22:58:31 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <CA+dvXXvQAFm_NHKStG4P8WOxWhM6DGYLcMMM9_B02iE5gsw_bg@mail.gmail.com>
References: <CA+dvXXuiL4+SRCZ5fqTr4WZ+pHhRaC9e=D7APBcZ2JGJZMiy6w@mail.gmail.com>
	<CAAo1mbnMTFf9pAyoY7dGGR5xKmZcEd6-nRZ9xyNNa3d5DoJLyg@mail.gmail.com>
	<CA+dvXXvQAFm_NHKStG4P8WOxWhM6DGYLcMMM9_B02iE5gsw_bg@mail.gmail.com>

Hi,

 

For your purpose, you should study using partitioning and postgres_fdw.

 

Regards

 

Michel SALAIS

De : Erik Serrano <[email protected]> 
Envoyé : mardi 5 novembre 2024 18:31
À : Samed YILDIRIM <[email protected]>
Cc : Pgsql-admin <[email protected]>; pgsql-admin <[email protected]>
Objet : Re: PostgreSQL historical database

 

 

Dear Sirs,

I'll tell you a little about what I need. Normally, during the day, records are made or recorded in the main database, which at the end of the day are consolidated (accounting closings) and are recorded in the database. In order not to make the main database grow without measure (which will only maintain the range between 3 months to 1 year). For this reason, this data must be transferred to another database so that it lasts over time and can be consulted by other areas. (This action is done humanly every day of the year at the end of the day)
Therefore, the project seeks to be able to carry out this extraction of the consolidated data to another database, but automatically.

I was thinking of doing this with some triggers or with jobs that allow me to carry out these actions. I also thought of creating a replication of only the consolidated tables to the new historical database server, but I have not yet defined the method.

That's why I need to know if there is a tool that allows me to create this database.

I hope this clarifies a little the scope of the new historical database.

Thank you very much in advance
Regards

 

 

Erik R. Serrano Saavedra

      Data Base Administrator

 

 

 

El mar, 5 nov 2024 a las 12:37, Samed YILDIRIM (<[email protected] <mailto:[email protected]> >) escribió:

Hello Erik,

 

It is not very clear for me what you are looking for. But, pg_bitemporal may be answer for you. I recommend to you to check the repository below. If this is not what you want, can you elaborate a little more?

 

https://github.com/hettie-d/pg_bitemporal

 

Best regards.
Samed YILDIRIM

 

On Tue, 5 Nov 2024, 17:31 Erik Serrano, <[email protected] <mailto:[email protected]> > wrote:

Dear,

Along with greetings, I would like to ask if there is any product, way (architecture), system that allows me to create a historical database from a main transactional database in PostgreSQL.

I thank you in advance for any contributions that help me to approach this new project.

Thank you very much, Guys,
Regards




 

Erik R. Serrano Saavedra

      Data Base Administrator

 

view thread (11+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: RE: PostgreSQL historical database
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox