-
Notifications
You must be signed in to change notification settings - Fork 2
/
Copy pathfeed.xml
154 lines (123 loc) · 8.78 KB
/
feed.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>ioguix' README</title>
<description>Blog posts from Jehan-Guillaume (ioguix) de Rorthais</description>
<link>http://blog.ioguix.net</link>
<atom:link href="http://blog.ioguix.net/feed.xml" rel="self" type="application/rss+xml" />
<item>
<title>Build a PostreSQL Automated Failover in 5 minutes</title>
<description><p>I’ve been working with <a href="https://www.vagrantup.com/">Vagrant</a> to quickly build a fresh
test cluster for <a href="https://clusterlabs.github.io/PAF/">PAF</a> development. Combined with
<code>virsh</code> snapshot related commands, I save a lot of time during my tons of tests by
quickly rollbacking the whole cluster to the initial state.</p>
<a href="http://blog.ioguix.net/postgresql/2019/01/24/Build-a-PostreSQL-Automated-Failover-in-5-minutes.html">Continue Reading »</a>
</description>
<pubDate>Thu, 24 Jan 2019 22:20:00 +0100</pubDate>
<link>http://blog.ioguix.net/postgresql/2019/01/24/Build-a-PostreSQL-Automated-Failover-in-5-minutes.html</link>
<guid isPermaLink="true">http://blog.ioguix.net/postgresql/2019/01/24/Build-a-PostreSQL-Automated-Failover-in-5-minutes.html</guid>
</item>
<item>
<title>PAF 2.2 rc1 released</title>
<description><p>The first release candidate of the PAF resource agent for Pacemaker has been
released yesterday.</p>
<a href="http://blog.ioguix.net/postgresql/2017/08/30/PAF-2-2-rc1-released.html">Continue Reading »</a>
</description>
<pubDate>Wed, 30 Aug 2017 14:00:00 +0200</pubDate>
<link>http://blog.ioguix.net/postgresql/2017/08/30/PAF-2-2-rc1-released.html</link>
<guid isPermaLink="true">http://blog.ioguix.net/postgresql/2017/08/30/PAF-2-2-rc1-released.html</guid>
</item>
<item>
<title>PAF, auto failover and more at PGConf.eu 2016</title>
<description><p>You will find the slides of my talk here: <a href="http://www.dalibo.org/_media/2016-pgconfeu-paf.html.gz">http://www.dalibo.org/_media/2016-pgconfeu-paf.html.gz</a></p>
<a href="http://blog.ioguix.net/postgresql/2016/11/02/PAF-auto-failover-and-more.html">Continue Reading »</a>
</description>
<pubDate>Wed, 02 Nov 2016 22:22:00 +0100</pubDate>
<link>http://blog.ioguix.net/postgresql/2016/11/02/PAF-auto-failover-and-more.html</link>
<guid isPermaLink="true">http://blog.ioguix.net/postgresql/2016/11/02/PAF-auto-failover-and-more.html</guid>
</item>
<item>
<title>New repository for bloat estimation queries</title>
<description><p>It’s been almost a year now that I wrote the first version of the btree bloat
estimation query. Then, came the first fixes, the bloat estimation queries for
tables, more fixes, and so on. Maintaining these queries as gists on github
was quite difficult and lack some features: no documented history, multiple
links, no doc, impossible to fork, etc.</p>
<a href="http://blog.ioguix.net/postgresql/2015/02/25/Bloat-queries-fixes-and-repository.html">Continue Reading »</a>
</description>
<pubDate>Wed, 25 Feb 2015 23:05:00 +0100</pubDate>
<link>http://blog.ioguix.net/postgresql/2015/02/25/Bloat-queries-fixes-and-repository.html</link>
<guid isPermaLink="true">http://blog.ioguix.net/postgresql/2015/02/25/Bloat-queries-fixes-and-repository.html</guid>
</item>
<item>
<title>Partitioning and constraints part 1 - UNIQUE</title>
<description><p>Partitioning in PostgreSQL has been an artisanal work for a long time now. And
despite the <a href="http://www.postgresql.org/message-id/[email protected]">current discussion</a>
running since few month on PostgreSQL’s hackers mailing list, it will probably
stay this way for some time again. Just because it requires a lot of brainstorm
and work.</p>
<a href="http://blog.ioguix.net/postgresql/2015/02/05/Partitionning-and-constraints-part-1.html">Continue Reading »</a>
</description>
<pubDate>Thu, 05 Feb 2015 09:30:00 +0100</pubDate>
<link>http://blog.ioguix.net/postgresql/2015/02/05/Partitionning-and-constraints-part-1.html</link>
<guid isPermaLink="true">http://blog.ioguix.net/postgresql/2015/02/05/Partitionning-and-constraints-part-1.html</guid>
</item>
<item>
<title>Btree bloat query - part 4</title>
<description><p>Thanks to the various PostgreSQL environments we have under monitoring at
Dalibo, these Btree bloat estimation queries keeps challenging me occasionally
because of statistics deviation…or bugs.</p>
<a href="http://blog.ioguix.net/postgresql/2014/11/03/Btree-bloat-query-part-4.html">Continue Reading »</a>
</description>
<pubDate>Mon, 03 Nov 2014 12:39:00 +0100</pubDate>
<link>http://blog.ioguix.net/postgresql/2014/11/03/Btree-bloat-query-part-4.html</link>
<guid isPermaLink="true">http://blog.ioguix.net/postgresql/2014/11/03/Btree-bloat-query-part-4.html</guid>
</item>
<item>
<title>Bloat estimation for tables</title>
<description><p>After my <a href="/postgresql/2014/09/10/Bloat-estimation-for-tables.html">Btree bloat estimation query</a>,
I found some time to work on a new query for tables. The goal here is still to
have a better bloat estimation using dedicated queries for each kind of objects.</p>
<a href="http://blog.ioguix.net/postgresql/2014/09/10/Bloat-estimation-for-tables.html">Continue Reading »</a>
</description>
<pubDate>Wed, 10 Sep 2014 18:30:00 +0200</pubDate>
<link>http://blog.ioguix.net/postgresql/2014/09/10/Bloat-estimation-for-tables.html</link>
<guid isPermaLink="true">http://blog.ioguix.net/postgresql/2014/09/10/Bloat-estimation-for-tables.html</guid>
</item>
<item>
<title>Btree bloat query changelog - part 3</title>
<description><p>Here are some fresh news about my previous work (see
<a href="/postgresql/2014/03/28/Playing-with-indexes-and-better-bloat-estimate.html">part 1</a>
and <a href="/postgresql/2014/06/24/More-work-on-index-bloat-estimation-query.html">part 2</a>)
on a better Btree bloat query.</p>
<a href="http://blog.ioguix.net/postgresql/2014/09/09/Btree-bloat-query-changelog-part-3.html">Continue Reading »</a>
</description>
<pubDate>Tue, 09 Sep 2014 17:00:00 +0200</pubDate>
<link>http://blog.ioguix.net/postgresql/2014/09/09/Btree-bloat-query-changelog-part-3.html</link>
<guid isPermaLink="true">http://blog.ioguix.net/postgresql/2014/09/09/Btree-bloat-query-changelog-part-3.html</guid>
</item>
<item>
<title>More work and thoughts on index bloat estimation query</title>
<description><p>A few weeks ago, I <a href="/postgresql/2014/03/28/Playing-with-indexes-and-better-bloat-estimate.html">published</a>
a query to estimate index bloat. Since then, I went back on this query a few
times to fix some drawbacks:</p>
<a href="http://blog.ioguix.net/postgresql/2014/06/24/More-work-on-index-bloat-estimation-query.html">Continue Reading »</a>
</description>
<pubDate>Tue, 24 Jun 2014 23:21:47 +0200</pubDate>
<link>http://blog.ioguix.net/postgresql/2014/06/24/More-work-on-index-bloat-estimation-query.html</link>
<guid isPermaLink="true">http://blog.ioguix.net/postgresql/2014/06/24/More-work-on-index-bloat-estimation-query.html</guid>
</item>
<item>
<title>Playing with indexes and better bloat estimate</title>
<description><p>Most of the PostgreSQL DBAs might know about <a href="http://wiki.postgresql.org/wiki/Show_database_bloat">this large bloat estimate query</a>
integrated in <a href="http://bucardo.org/wiki/Check_postgres">check_postgres</a>. It is
supposed to compute a rough estimate of the bloat for tables and indexes in a
database. As the PostgreSQL wiki page says:</p>
<a href="http://blog.ioguix.net/postgresql/2014/03/28/Playing-with-indexes-and-better-bloat-estimate.html">Continue Reading »</a>
</description>
<pubDate>Fri, 28 Mar 2014 07:05:00 +0100</pubDate>
<link>http://blog.ioguix.net/postgresql/2014/03/28/Playing-with-indexes-and-better-bloat-estimate.html</link>
<guid isPermaLink="true">http://blog.ioguix.net/postgresql/2014/03/28/Playing-with-indexes-and-better-bloat-estimate.html</guid>
</item>
</channel>
</rss>