Re: How to shorten a chain of logically replicated servers

> You'd have to suspend all data modification on A in that interval. I know how to stop the DB completely, but I can't think of any obvious ways to make sure that it doesn't get any data modification for a period of time. Is there a trick here? This is feeling a bit hopeless. Thanks for the respo

Setting up an environment of EDB Advance server

Hi team, We would need your help in setting up an environment of EDB Advance Server 11 on Dev CentOS 7 VM. 1. We need to create three database with separate table spaces : Test1 Test2 Test3 What would be the good strategy for the setup with regards to the tablespaces? Can we create a separ

Re: jsonb_set() strictness considered harmful to data

On Wed, Jan 8, 2020 at 7:08 AM Pavel Stehule wrote: > > Hi > > po 6. 1. 2020 v 22:34 odesílatel Andrew Dunstan > napsal: >> >> >> Updated version including docco and better error message. >> >> cheers >> >> andrew > > > I think so my objections are solved. I have small objection > > + errdetail(

Postgres streaming replication

Hello team, I have to implement the streaming replication for our prod environment. Can you please share the list of parameters to setup the PostgreSQL 11 streaming replication with continuous archiving and give clarity on the below. * Do we need to enable the archive_mode and archive_comma

Re: Upgrade PostgreSQL 9.6 to 10.6

On Tue, Dec 10, 2019 at 2:53 AM Andreas Kretschmer wrote: > > > Am 09.12.19 um 23:37 schrieb github kran: > > Great, thanks Andreas, So this seems to be a good feature using the > > core concept of replication. Can I use this extension and do the major > > upgrade without paying ?. > > yes, this

Re: UPDATE many records

> > On Jan 7, 2020, at 12:57 PM, Adrian Klaver wrote: > > On 1/7/20 1:43 PM, Israel Brewster wrote: >>> On Jan 7, 2020, at 12:21 PM, Adrian Klaver >> > wrote: >>> >>> On 1/7/20 1:10 PM, Israel Brewster wrote: > On Jan 7, 2020, at 12:01 PM, Adrian Klaver >>>

Re: UPDATE many records

On 1/7/20 1:43 PM, Israel Brewster wrote: On Jan 7, 2020, at 12:21 PM, Adrian Klaver > wrote: On 1/7/20 1:10 PM, Israel Brewster wrote: On Jan 7, 2020, at 12:01 PM, Adrian Klaver mailto:adrian.kla...@aklaver.com>> wrote: On 1/7/20 12:47 PM, Israel Brewster wr

Re: UPDATE many records

> On Jan 7, 2020, at 12:21 PM, Adrian Klaver wrote: > > On 1/7/20 1:10 PM, Israel Brewster wrote: >>> On Jan 7, 2020, at 12:01 PM, Adrian Klaver >>> wrote: >>> >>> On 1/7/20 12:47 PM, Israel Brewster wrote: One potential issue I just thought of with this approach: disk space. Will I

Re: UPDATE many records

On 1/7/20 1:10 PM, Israel Brewster wrote: On Jan 7, 2020, at 12:01 PM, Adrian Klaver wrote: On 1/7/20 12:47 PM, Israel Brewster wrote: One potential issue I just thought of with this approach: disk space. Will I be doubling the amount of space used while both tables exist? If so, that would

Re: UPDATE many records

> On Jan 7, 2020, at 12:15 PM, Alan Hodgson wrote: > > On Tue, 2020-01-07 at 11:58 -0900, Israel Brewster wrote: >>> >> Really? Why? With the update I am only changing data - I’m not adding >> any additional data, so the total size should stay the same, right? >> I’m obviously missing something…

Re: UPDATE many records

On Tue, 2020-01-07 at 11:58 -0900, Israel Brewster wrote: > > > Really? Why? With the update I am only changing data - I’m not adding > any additional data, so the total size should stay the same, right? > I’m obviously missing something… :-) > PostgreSQL keeps the old row until it gets vacuumed

Re: UPDATE many records

> On Jan 7, 2020, at 12:01 PM, Adrian Klaver wrote: > > On 1/7/20 12:47 PM, Israel Brewster wrote: >> One potential issue I just thought of with this approach: disk space. Will I >> be doubling the amount of space used while both tables exist? If so, that >> would prevent this from working -

Re: UPDATE many records

On 1/7/20 12:58 PM, Israel Brewster wrote: On Jan 7, 2020, at 11:56 AM, Alan Hodgson wrote: On Tue, 2020-01-07 at 11:47 -0900, Israel Brewster wrote: One potential issue I just thought of with this approach: disk space. Will I be doubling the amount of space used while both tables exist? If so

Re: UPDATE many records

On 1/7/20 12:47 PM, Israel Brewster wrote: One potential issue I just thought of with this approach: disk space. Will I be doubling the amount of space used while both tables exist? If so, that would prevent this from working - I don’t have that much space available at the moment. It will def

Re: UPDATE many records

On Tue, 2020-01-07 at 11:47 -0900, Israel Brewster wrote: > One potential issue I just thought of with this approach: disk space. > Will I be doubling the amount of space used while both tables exist? > If so, that would prevent this from working - I don’t have that much > space available at the mo

Re: UPDATE many records

> On Jan 7, 2020, at 11:56 AM, Alan Hodgson wrote: > > On Tue, 2020-01-07 at 11:47 -0900, Israel Brewster wrote: >> One potential issue I just thought of with this approach: disk space. >> Will I be doubling the amount of space used while both tables exist? >> If so, that would prevent this from

Re: Writing Postgres Extensions in C on Windows

On Wed, Jan 8, 2020 at 4:32 AM İlyas Derse wrote: > I want to register C code to PostgreSql on Windows. So I think, I have to > make a extension for PostgreSql. But I did not find to written extension on > windows. Do you have an idea ? I don't do Windows myself but this blog from Craig Ringer

Re: UPDATE many records

One potential issue I just thought of with this approach: disk space. Will I be doubling the amount of space used while both tables exist? If so, that would prevent this from working - I don’t have that much space available at the moment. --- Israel Brewster Software Engineer Alaska Volcano Obse

Re: jsonb_set() strictness considered harmful to data

Hi po 6. 1. 2020 v 22:34 odesílatel Andrew Dunstan < andrew.duns...@2ndquadrant.com> napsal: > On Thu, Nov 28, 2019 at 2:15 PM Andrew Dunstan > wrote: > > > > > > On 11/27/19 9:35 PM, Michael Paquier wrote: > > > On Fri, Nov 15, 2019 at 09:45:59PM +0100, Pavel Stehule wrote: > > >> Maybe ERRCODE

Re: UPDATE many records

Nice approach! Using that method, I can do the select to generate the new table in only 6 minutes! I’m sure it helps that through a slightly creative use of Joins, I can re-write my function to actually be part of the select, just using bult-in trig functions, rather than having to called a stor

RE: UPDATE many records

You don’t tell us if other users will be concurrently changing any of the records involved. If you could guarantee that the table won’t be changed, you might be better off doing a CREATE TABLE table_new as SELECT … FROM table_old, dropping table_old, and finally renaming table_new. Given the

Writing Postgres Extensions in C on Windows

I want to register C code to PostgreSql on Windows. So I think, I have to make a extension for PostgreSql. But I did not find to written extension on windows. Do you have an idea ? Thanks ...

Re: How to reset a server error '25P02 in_failed_sql_transaction'

On Tue, 2019-12-31 at 06:55 +0100, Matthias Apitz wrote: > Due to a wrong human input in the GUI of our application our > application server, from the point of view of the PostgreSQL server it > is the PostgreSQL client, issues a broken ESQL/C command to the PostgreSQL > server, here from our own d

Re: How to shorten a chain of logically replicated servers

On Tue, 2019-12-31 at 15:51 -0800, Mike Lissner wrote: > Hi, I'm trying to figure out how to shorten a chain of logically > replicating servers. Right now we have three servers replicating like > so: > > A --> B --> C > > And I'd like to remove B from the chain of replication so that I only have: