pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ron <ronljohnsonjr@gmail.com>
To: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: Re: Delete Enhancement Request
Date: Tue, 15 Jan 2019 12:48:04 -0600
Message-ID: <61fbb5a9-5285-b7c8-e6d7-f1a68bb59c20@gmail.com> (raw)
In-Reply-To: <CAGDYbUMj06JYF+XLiaba36JyCgTa3iViJaXDjS2MiqKofB9gZg@mail.gmail.com>
References: <EE8A78ED-B910-4FC0-BE85-39F74B90A055@illinois.edu>
	<3f7591ea-9747-1ac6-4299-13fe66216ef2@gmail.com>
	<315D458B-936D-4335-BB31-D194EC36567E@digitalapicraft.com>
	<CAGDYbUMj06JYF+XLiaba36JyCgTa3iViJaXDjS2MiqKofB9gZg@mail.gmail.com>

Which is a 3rd party tool.

On 1/15/19 11:10 AM, Shreeyansh Dba wrote:
> Hi Sridhara,
>
> For an incremental backup, you can use pgBackRest.
>
> Please go through the below link...
> https://pgbackrest.org/
>
> Thanks & Regards,
> *Shreeyansh DBA Team*
> www.shreeyansh.com <http://www.shreeyansh.com;
>
>
> On Tue, Jan 15, 2019 at 9:26 PM Sridhara KB 
> <sridhara.kb@digitalapicraft.com <mailto:sridhara.kb@digitalapicraft.com>> 
> wrote:
>
>     Hi can anyone help me to get incremental backup without using third
>     party tool like barman , rman etc...
>
>     Thank you,
>     Sridhara k.b
>
>     On 14-Jan-2019, at 9:38 PM, Ron <ronljohnsonjr@gmail.com
>     <mailto:ronljohnsonjr@gmail.com>> wrote:
>
>>     On 1/14/19 9:18 AM, Campbell, Lance wrote:
>>>
>>>     Please consider adding this feature to PostgreSQL.
>>>
>>>     Use Case:
>>>
>>>     When deleting a large number of records with constraints and
>>>     triggers PostgreSQL is exceptionally slow.
>>>
>>>     Suggested change:
>>>
>>>     I believe a way to speed this processes up would be to offer an
>>>     option a user could “turn on” prior to doing the delete.
>>>
>>>     Example: set delete-no-roll-back=true
>>>
>>>     Now as PostgreSQL deletes rows it literally deletes them one at a
>>>     time as though the user was only deleting a single row.  This means
>>>     that if cancel were executed on a delete action then it would only
>>>     roll back the current row that PostgreSQL was in the process of
>>>     deleting. Example:  if you had 10 million row to delete and then
>>>     pressed cancel after three minutes maybe 5 million are deleted.
>>>
>>
>>     You seem to be asking for an unlogged transaction, but that doesn't
>>     have anything to do with efficiently deleting rows.
>>
>>
>>     -- 
>>     Angular momentum makes the world go 'round.
>

-- 
Angular momentum makes the world go 'round.

view thread (9+ messages)  latest in thread

Message-ID: <61fbb5a9-5285-b7c8-e6d7-f1a68bb59c20@gmail.com>
Permalink:  ../61fbb5a9-5285-b7c8-e6d7-f1a68bb59c20@gmail.com/
Also on:    postgresql.org/message-id/61fbb5a9-5285-b7c8-e6d7-f1a68bb59c20@gmail.com

 · 

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: pgsql-admin@postgresql.org
  Cc: ronljohnsonjr@gmail.com, pgsql-admin@lists.postgresql.org
  Subject: Re: Delete Enhancement Request
  In-Reply-To: <61fbb5a9-5285-b7c8-e6d7-f1a68bb59c20@gmail.com>

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

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