Re: Doubts about replication..

2018-04-20 Thread Stefan Fercot
Hi,

If you want to reduce the amount of data lost, you might want to
consider another type of backup :
https://www.postgresql.org/docs/current/static/continuous-archiving.html

That awsome tool can also help you with it : https://pgbackrest.org/


On 04/19/2018 08:48 PM, Edmundo Robles wrote:
> Yes, you are right, the replication is not  a backup ;)  , actually 
>  i backup  database  daily at  3:00 am but if database crash,  the
> amount  of data is  big!  that is the reason i want to  replicate to
> reduce  the data loss. By the way  a few days ago a job partner did a
> delete with no where.
>
> On Thu, Apr 19, 2018 at 1:33 PM, Andreas Kretschmer
> mailto:andr...@a-kretschmer.de>> wrote:
>
>
>
> Am 19.04.2018 um 19:57 schrieb Edmundo Robles:
>
> I will use replication as simple backup.
>
>
> please keep in mind, replication is not a backup. All logical
> errors on the master (delete from table and forgot the
> where-condition) will replicated to the standby.
>
>
> Andreas
>
> -- 
> 2ndQuadrant - The PostgreSQL Support Company.
> www.2ndQuadrant.com <http://www.2ndQuadrant.com>
>
>
>
>
>
> -- 
>

Kind regards,

-- 
Stefan FERCOT
http://dalibo.com - http://dalibo.org



signature.asc
Description: OpenPGP digital signature


Re: Proposed Translations of Updated Code of Conduct Policy

2022-07-18 Thread Stefan Fercot
Hi,

There's a typo in the french translation. "consécutis" should be "consécutifs".

And per consistency, I'd suggest to not mix "mandat" and "termes" to speak 
about the same thing. I believe it would be better to replace "(3) termes 
consécutis" by "(3) mandats consécutifs".

--
Kind Regards,

Stefan FERCOT
EDB: [https://www.enterprisedb.com](https://www.enterprisedb.com/)

--- Original Message ---
Le samedi 16 juillet 2022 à 7:24 PM, Lucie Šimečková 
 a écrit :

> Hello all,
>
> Following the recent update of the English version of the Code of Conduct 
> that clarified the term limits of CoC committee members, the PostgreSQL 
> Community Code of Conduct Committee has solicited translations of the updated 
> CoC.
>
> The English version of the Policy is at:
>
> https://www.postgresql.org/about/policies/coc/
>
> The following translations were contributed by:
>
> - German translation provided by Andreas Scherbaum
> - French translation provided by Guillaume Lelarge
> - Hebrew translation provided by Michael Goldberg
> - Italian translation provided by Federico Campoli and reviewed by Tommaso 
> Bartoli
> - Russian translation provided by Alexander Lakhin
> - Chinese translation provided by Bo Peng
> - Japanese translation provided by Tatsuo Ishii
>
> The proposed translations are attached as plain text and PDF files to this 
> message.
>
> If you have any comments or suggestions for the proposed translations, please 
> bring them to our attention no later than 11:59 PM UTC on Sunday, July 24, 
> 2022. What time is that in my time zone? 
> https://www.timeanddate.com/worldclock/converter.html?iso=20220724T23&p1=1440
>
> Thank you!
>
> Lucie Šimečková
>
> PostgreSQL Community Code of Conduct Committee Member

Re: Table and Index bloating

2017-11-27 Thread Stefan Fercot
Hi,

You can track that with some monitoring tools like check_pgactivity. The
queries can be found here :
https://github.com/ioguix/pgsql-bloat-estimation.

Tables :
https://github.com/ioguix/pgsql-bloat-estimation/blob/master/table/table_bloat.sql
Indexes :
https://github.com/ioguix/pgsql-bloat-estimation/blob/master/btree/btree_bloat.sql

Backups should also be part of your maintenance plan.
Vacuum/Analyse/Reindex is already a good basis.


Kind regards


On 11/27/2017 10:10 AM, Vikas Sharma wrote:
> Hi All,
>
> Could someone please provide the query/queries  to find table and
> Index bloating in PgSql 9.3 onwards? 
> and are there any other maintenance tasks inPgSql except vacuum & analyse.
>
> Regards
> Vikas

-- 
Stefan FERCOT
http://dalibo.com - http://dalibo.org




signature.asc
Description: OpenPGP digital signature