Re: Delete Enhancement Request

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(dot)kb(at)digitalapicraft(dot)com <mailto:sridhara(dot)kb(at)digitalapicraft(dot)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(at)gmail(dot)com
> <mailto:ronljohnsonjr(at)gmail(dot)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.