On 02/08/22, Robert Blayzor (rblayzor.b...@inoc.net) wrote:
> On 8/2/22 10:57, Rory Campbell-Lange wrote:
> > Special care must be taken with the "replica identity" of published
> > tables, as set out at
> > https://www.postgresql.org/docs/current/logical-replic
On 02/08/22, Robert Blayzor (rblayzor.b...@inoc.net) wrote:
> Is it possible to have a single subscriber table contact multiple publishers
> and just insert all of the data into a single table on the subscriber? ie:
> merge type replication. There are no primary/FK constraints, etc. The
> records
On 16/07/22, Rory Campbell-Lange (r...@campbell-lange.net) wrote:
> I'd be grateful for some comments on the advisability of using a large
> number of concurrent logical replication publications/subscriptions.
> Below I've set out the current environment and a suggested design.
&g
On 17/07/22, Rick Otten (rottenwindf...@gmail.com) wrote:
> On Sat, Jul 16, 2022 at 12:07 PM Rory Campbell-Lange <
> r...@campbell-lange.net> wrote:
>
> > I'd be grateful for some comments on the advisability of using a large
> > number of concurrent logical replication
I'd be grateful for some comments on the advisability of using a large
number of concurrent logical replication publications/subscriptions.
Below I've set out the current environment and a suggested design.
Apologies for the length of this email.
We presently have many hundreds of small databases
On 15/06/21, Haseeb Khan (khanhasee...@gmail.com) wrote:
> I have confusion below, Should we create an archive path on the standby
> server and then set it to recovery.conf file ?
>
> restore_command = 'cp /path/to/archive/%f %p'
Hi Hasseb
Are you following this procedure?
On 15/06/21, Haseeb Khan (khanhasee...@gmail.com) wrote:
> Does anyone have complete documentation to configure PostgreSQL V13 Master
> and Slave on Windows Server and also how to test Manual Failover ?
I suggest having a look at
https://www.postgresql.org/docs/13/high-availability.html
The
On 26/04/21, Marc Millas (marc.mil...@mokadb.com) wrote:
> compression ?
>
> I am currently working on a project to move an oracle db to postgres.
> The db is 15 TB.
> with Oracle compression it does use 5 TB of disk space.
>
> If we cannot compress the whole thing, the project loses its
On 24/04/21, Christophe Pettus (x...@thebuild.com) wrote:
> > On Apr 24, 2021, at 11:27, Simon Connah
> > wrote:
> >
> > I'm curious, really. I use btrfs as my filesystem on my home systems and am
> > setting up a server as I near releasing my project. I planned to use btrfs
> > on the
Apologies for the cross-post to the general list.
I'm keen to know if there are any good reasons apart from disk space and
possible replication connection overhead to avoid the strategy proposed
below.
We have quite a few databases of type a and many of type b in a cluster.
Both a and b types
We're buying some new Postgres servers with
2 x 240GB Intel SSD S4610 (RAID1 : system)
4 x 960GB Intel SSD S4610 (RAID10 : db)
We'll be using Postgres 11 on Debian.
We aren't sure whether to use MDRaid or a MegaRAID card
The MegaRAID 9271-8i with flash cache protection is available
Apologies for the cross-post to the general list. I realised I should
have (possibly?) posted here instead. Advice gratefully received.
We've been happy running a database server and replica for some years
with the following details and specs:
postgres 9.5 (currently)
supermicro
It is some time since I've written to the postgres lists. My apologies
if this is the wrong list to post this to.
We are looking to upgrade our current database server infrastructure so
that it is suitable for the next 3 years or so.
Presently we have two physical servers with the same specs:
13 matches
Mail list logo
