際際滷shows by User: PostgreSQL-Consulting / http://www.slideshare.net/images/logo.gif 際際滷shows by User: PostgreSQL-Consulting / Thu, 26 Oct 2017 08:51:44 GMT 際際滷Share feed for 際際滷shows by User: PostgreSQL-Consulting Ilya Kosmodemiansky - An ultimate guide to upgrading your PostgreSQL installation PGConf.EU /slideshow/ilya-kosmodemiansky-an-ultimate-guide-to-upgrading-your-postgresql-installation-pgconfeu/81232750 kosmodemianskyupgrades-171026085144
Even an experienced PostgreSQL DBA can not always say that upgrading between major versions of Postgres is an easy task, especially if there are some special requirements, such as downtime limitations or if something goes wrong. For less experienced DBAs anything more complex than dump/restore can be frustrating. In this talk I will describe why we need a special procedure to upgrade between major versions, how that can be achieved and what sort of problems can occur. I will review all possible ways to upgrade your cluster from classical pg_upgrade to old-school slony or modern methods like logical replication. For all approaches, I will give a brief explanation how it works (limited by the scope of this talk of course), examples how to perform upgrade and some advice on potentially problematic steps. Besides I will touch upon such topics as integration of upgrade tools and procedures with other software connection brokers, operating system package managers, automation tools, etc. This talk would not be complete if I do not cover cases when something goes wrong and how to deal with such cases. ]]>
Even an experienced PostgreSQL DBA can not always say that upgrading between major versions of Postgres is an easy task, especially if there are some special requirements, such as downtime limitations or if something goes wrong. For less experienced DBAs anything more complex than dump/restore can be frustrating. In this talk I will describe why we need a special procedure to upgrade between major versions, how that can be achieved and what sort of problems can occur. I will review all possible ways to upgrade your cluster from classical pg_upgrade to old-school slony or modern methods like logical replication. For all approaches, I will give a brief explanation how it works (limited by the scope of this talk of course), examples how to perform upgrade and some advice on potentially problematic steps. Besides I will touch upon such topics as integration of upgrade tools and procedures with other software connection brokers, operating system package managers, automation tools, etc. This talk would not be complete if I do not cover cases when something goes wrong and how to deal with such cases. ]]> Thu, 26 Oct 2017 08:51:44 GMT /slideshow/ilya-kosmodemiansky-an-ultimate-guide-to-upgrading-your-postgresql-installation-pgconfeu/81232750 PostgreSQL-Consulting@slideshare.net(PostgreSQL-Consulting) Ilya Kosmodemiansky - An ultimate guide to upgrading your PostgreSQL installation PGConf.EU PostgreSQL-Consulting Even an experienced PostgreSQL DBA can not always say that upgrading between major versions of Postgres is an easy task, especially if there are some special requirements, such as downtime limitations or if something goes wrong. For less experienced DBAs anything more complex than dump/restore can be frustrating. In this talk I will describe why we need a special procedure to upgrade between major versions, how that can be achieved and what sort of problems can occur. I will review all possible ways to upgrade your cluster from classical pg_upgrade to old-school slony or modern methods like logical replication. For all approaches, I will give a brief explanation how it works (limited by the scope of this talk of course), examples how to perform upgrade and some advice on potentially problematic steps. Besides I will touch upon such topics as integration of upgrade tools and procedures with other software connection brokers, operating system package managers, automation tools, etc. This talk would not be complete if I do not cover cases when something goes wrong and how to deal with such cases. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/kosmodemianskyupgrades-171026085144-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Even an experienced PostgreSQL DBA can not always say that upgrading between major versions of Postgres is an easy task, especially if there are some special requirements, such as downtime limitations or if something goes wrong. For less experienced DBAs anything more complex than dump/restore can be frustrating. In this talk I will describe why we need a special procedure to upgrade between major versions, how that can be achieved and what sort of problems can occur. I will review all possible ways to upgrade your cluster from classical pg_upgrade to old-school slony or modern methods like logical replication. For all approaches, I will give a brief explanation how it works (limited by the scope of this talk of course), examples how to perform upgrade and some advice on potentially problematic steps. Besides I will touch upon such topics as integration of upgrade tools and procedures with other software connection brokers, operating system package managers, automation tools, etc. This talk would not be complete if I do not cover cases when something goes wrong and how to deal with such cases.
Ilya Kosmodemiansky - An ultimate guide to upgrading your PostgreSQL installation PGConf.EU from PostgreSQL-Consulting
]]> 2474 6 https://cdn.slidesharecdn.com/ss_thumbnails/kosmodemianskyupgrades-171026085144-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Linux IO internals for database administrators (SCaLE 2017 and PGDay Nordic 2017 version) /slideshow/linux-io-internals-for-database-administrators-scale-2017-and-pgday-nordic-2017-version/74095743 scale2017kosmodemiansky-170331191144
Input-output performance problems are on every day agenda for DBAs since the databases exist. Volume of data grows rapidly and you need to get your data fast from the disk and moreover - fast to the disk. For most databases there is a more or less easy to find checklist of recommended Linux settings to maximize IO throughput. In most cases that checklist is good enough. But it is always better to understand how it works, especially if you run into some corner-cases. This talk is about how IO in Linux works, how database pages travel from disk level to database own shared memory and back and what kind of mechanisms exist to control this. We will discuss memory structures, swap and page-out daemons, filesystems, schedulers and IO methods. Some fundamental differences in IO approaches between PostgreSQL, Oracle and MySQL will be covered]]>
Input-output performance problems are on every day agenda for DBAs since the databases exist. Volume of data grows rapidly and you need to get your data fast from the disk and moreover - fast to the disk. For most databases there is a more or less easy to find checklist of recommended Linux settings to maximize IO throughput. In most cases that checklist is good enough. But it is always better to understand how it works, especially if you run into some corner-cases. This talk is about how IO in Linux works, how database pages travel from disk level to database own shared memory and back and what kind of mechanisms exist to control this. We will discuss memory structures, swap and page-out daemons, filesystems, schedulers and IO methods. Some fundamental differences in IO approaches between PostgreSQL, Oracle and MySQL will be covered]]> Fri, 31 Mar 2017 19:11:44 GMT /slideshow/linux-io-internals-for-database-administrators-scale-2017-and-pgday-nordic-2017-version/74095743 PostgreSQL-Consulting@slideshare.net(PostgreSQL-Consulting) Linux IO internals for database administrators (SCaLE 2017 and PGDay Nordic 2017 version) PostgreSQL-Consulting Input-output performance problems are on every day agenda for DBAs since the databases exist. Volume of data grows rapidly and you need to get your data fast from the disk and moreover - fast to the disk. For most databases there is a more or less easy to find checklist of recommended Linux settings to maximize IO throughput. In most cases that checklist is good enough. But it is always better to understand how it works, especially if you run into some corner-cases. This talk is about how IO in Linux works, how database pages travel from disk level to database own shared memory and back and what kind of mechanisms exist to control this. We will discuss memory structures, swap and page-out daemons, filesystems, schedulers and IO methods. Some fundamental differences in IO approaches between PostgreSQL, Oracle and MySQL will be covered <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/scale2017kosmodemiansky-170331191144-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Input-output performance problems are on every day agenda for DBAs since the databases exist. Volume of data grows rapidly and you need to get your data fast from the disk and moreover - fast to the disk. For most databases there is a more or less easy to find checklist of recommended Linux settings to maximize IO throughput. In most cases that checklist is good enough. But it is always better to understand how it works, especially if you run into some corner-cases. This talk is about how IO in Linux works, how database pages travel from disk level to database own shared memory and back and what kind of mechanisms exist to control this. We will discuss memory structures, swap and page-out daemons, filesystems, schedulers and IO methods. Some fundamental differences in IO approaches between PostgreSQL, Oracle and MySQL will be covered
Linux IO internals for database administrators (SCaLE 2017 and PGDay Nordic 2017 version) from PostgreSQL-Consulting
]]> 1070 3 https://cdn.slidesharecdn.com/ss_thumbnails/scale2017kosmodemiansky-170331191144-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 PostgreSQL worst practices, version PGConf.US 2017 by Ilya Kosmodemiansky /PostgreSQL-Consulting/postgresql-worst-practices-version-pgconfus-2017-by-ilya-kosmodemiansky pgconfus2017kosmodemiansky-170331190504
This talk is prepared as a bunch of slides, where each slide describes a really bad way people can screw up their PostgreSQL database and provides a weight - how frequently I saw that kind of problem. Right before the talk I will reshuffle the deck to draw twenty random slides and explain you why such practices are bad and how to avoid running into them.]]>
This talk is prepared as a bunch of slides, where each slide describes a really bad way people can screw up their PostgreSQL database and provides a weight - how frequently I saw that kind of problem. Right before the talk I will reshuffle the deck to draw twenty random slides and explain you why such practices are bad and how to avoid running into them.]]> Fri, 31 Mar 2017 19:05:04 GMT /PostgreSQL-Consulting/postgresql-worst-practices-version-pgconfus-2017-by-ilya-kosmodemiansky PostgreSQL-Consulting@slideshare.net(PostgreSQL-Consulting) PostgreSQL worst practices, version PGConf.US 2017 by Ilya Kosmodemiansky PostgreSQL-Consulting This talk is prepared as a bunch of slides, where each slide describes a really bad way people can screw up their PostgreSQL database and provides a weight - how frequently I saw that kind of problem. Right before the talk I will reshuffle the deck to draw twenty random slides and explain you why such practices are bad and how to avoid running into them. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/pgconfus2017kosmodemiansky-170331190504-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> This talk is prepared as a bunch of slides, where each slide describes a really bad way people can screw up their PostgreSQL database and provides a weight - how frequently I saw that kind of problem. Right before the talk I will reshuffle the deck to draw twenty random slides and explain you why such practices are bad and how to avoid running into them.
PostgreSQL worst practices, version PGConf.US 2017 by Ilya Kosmodemiansky from PostgreSQL-Consulting
]]> 1374 3 https://cdn.slidesharecdn.com/ss_thumbnails/pgconfus2017kosmodemiansky-170331190504-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 PostgreSQL worst practices, version FOSDEM PGDay 2017 by Ilya Kosmodemiansky /slideshow/postgresql-worst-practices-version-fosdem-pgday-2017-by-ilya-kosmodemiansky/71901044 pwpkosmodemiansky-170208085608
This talk is prepared as a bunch of slides, where each slide describes a really bad way people can screw up their PostgreSQL database and provides a weight - how frequently I saw that kind of problem. Right before the talk I will reshuffle the deck to draw ten random slides and explain you why such practices are bad and how to avoid running into them. ]]>
This talk is prepared as a bunch of slides, where each slide describes a really bad way people can screw up their PostgreSQL database and provides a weight - how frequently I saw that kind of problem. Right before the talk I will reshuffle the deck to draw ten random slides and explain you why such practices are bad and how to avoid running into them. ]]> Wed, 08 Feb 2017 08:56:08 GMT /slideshow/postgresql-worst-practices-version-fosdem-pgday-2017-by-ilya-kosmodemiansky/71901044 PostgreSQL-Consulting@slideshare.net(PostgreSQL-Consulting) PostgreSQL worst practices, version FOSDEM PGDay 2017 by Ilya Kosmodemiansky PostgreSQL-Consulting This talk is prepared as a bunch of slides, where each slide describes a really bad way people can screw up their PostgreSQL database and provides a weight - how frequently I saw that kind of problem. Right before the talk I will reshuffle the deck to draw ten random slides and explain you why such practices are bad and how to avoid running into them. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/pwpkosmodemiansky-170208085608-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> This talk is prepared as a bunch of slides, where each slide describes a really bad way people can screw up their PostgreSQL database and provides a weight - how frequently I saw that kind of problem. Right before the talk I will reshuffle the deck to draw ten random slides and explain you why such practices are bad and how to avoid running into them.
PostgreSQL worst practices, version FOSDEM PGDay 2017 by Ilya Kosmodemiansky from PostgreSQL-Consulting
]]> 13922 8 https://cdn.slidesharecdn.com/ss_thumbnails/pwpkosmodemiansky-170208085608-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Linux internals for Database administrators at Linux Piter 2016 /slideshow/linux-internals-for-database-administrators-at-linux-piter-2016/68763333 linuxpiter2016kosmodemianskylinux-161112071339
Input-output performance problems are on every day agenda for DBAs since the databases exist. Volume of data grows rapidly and you need to get your data fast from the disk and moreover - fast to the disk. For most databases there is a more or less easy to find checklist of recommended Linux settings to maximize IO throughput. In most cases that checklist is good enough. But it is always better to understand how it works, especially if you run into some corner-cases. This talk is about how IO in Linux works, how database pages travel from disk level to database own shared memory and back and what kind of mechanisms exist to control this. We will discuss memory structures, swap and page-out daemons, filesystems, schedullers and IO methods. Some fundamental differences in IO approaches between PostgreSQL, Oracle and MySQL will be covered.]]>
Input-output performance problems are on every day agenda for DBAs since the databases exist. Volume of data grows rapidly and you need to get your data fast from the disk and moreover - fast to the disk. For most databases there is a more or less easy to find checklist of recommended Linux settings to maximize IO throughput. In most cases that checklist is good enough. But it is always better to understand how it works, especially if you run into some corner-cases. This talk is about how IO in Linux works, how database pages travel from disk level to database own shared memory and back and what kind of mechanisms exist to control this. We will discuss memory structures, swap and page-out daemons, filesystems, schedullers and IO methods. Some fundamental differences in IO approaches between PostgreSQL, Oracle and MySQL will be covered.]]> Sat, 12 Nov 2016 07:13:39 GMT /slideshow/linux-internals-for-database-administrators-at-linux-piter-2016/68763333 PostgreSQL-Consulting@slideshare.net(PostgreSQL-Consulting) Linux internals for Database administrators at Linux Piter 2016 PostgreSQL-Consulting Input-output performance problems are on every day agenda for DBAs since the databases exist. Volume of data grows rapidly and you need to get your data fast from the disk and moreover - fast to the disk. For most databases there is a more or less easy to find checklist of recommended Linux settings to maximize IO throughput. In most cases that checklist is good enough. But it is always better to understand how it works, especially if you run into some corner-cases. This talk is about how IO in Linux works, how database pages travel from disk level to database own shared memory and back and what kind of mechanisms exist to control this. We will discuss memory structures, swap and page-out daemons, filesystems, schedullers and IO methods. Some fundamental differences in IO approaches between PostgreSQL, Oracle and MySQL will be covered. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/linuxpiter2016kosmodemianskylinux-161112071339-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Input-output performance problems are on every day agenda for DBAs since the databases exist. Volume of data grows rapidly and you need to get your data fast from the disk and moreover - fast to the disk. For most databases there is a more or less easy to find checklist of recommended Linux settings to maximize IO throughput. In most cases that checklist is good enough. But it is always better to understand how it works, especially if you run into some corner-cases. This talk is about how IO in Linux works, how database pages travel from disk level to database own shared memory and back and what kind of mechanisms exist to control this. We will discuss memory structures, swap and page-out daemons, filesystems, schedullers and IO methods. Some fundamental differences in IO approaches between PostgreSQL, Oracle and MySQL will be covered.
Linux internals for Database administrators at Linux Piter 2016 from PostgreSQL-Consulting
]]> 1514 4 https://cdn.slidesharecdn.com/ss_thumbnails/linuxpiter2016kosmodemianskylinux-161112071339-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 10 things, an Oracle DBA should care about when moving to PostgreSQL /slideshow/10-things-an-oracle-dba-should-care-about-when-moving-to-postgresql/60332471 pgdaypariskosmodemiansky-160401092849
PGDay Paris 2016 by Ilya Kosmodemiansky]]>
PGDay Paris 2016 by Ilya Kosmodemiansky]]> Fri, 01 Apr 2016 09:28:49 GMT /slideshow/10-things-an-oracle-dba-should-care-about-when-moving-to-postgresql/60332471 PostgreSQL-Consulting@slideshare.net(PostgreSQL-Consulting) 10 things, an Oracle DBA should care about when moving to PostgreSQL PostgreSQL-Consulting PGDay Paris 2016 by Ilya Kosmodemiansky <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/pgdaypariskosmodemiansky-160401092849-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> PGDay Paris 2016 by Ilya Kosmodemiansky
10 things, an Oracle DBA should care about when moving to PostgreSQL from PostgreSQL-Consulting
]]> 3265 6 https://cdn.slidesharecdn.com/ss_thumbnails/pgdaypariskosmodemiansky-160401092849-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Autovacuum, explained for engineers, new improved version PGConf.eu 2015 Vienna /slideshow/autovacuum-explained-for-engineers-new-improved-version-pgconfeu-2015-vienna/54561568 pgconfeukosmodemianskyvacuum-151030110722-lva1-app6891
How to configure PostgreSQL autovacuum by Ilya Kosmodemiansky]]>
How to configure PostgreSQL autovacuum by Ilya Kosmodemiansky]]> Fri, 30 Oct 2015 11:07:22 GMT /slideshow/autovacuum-explained-for-engineers-new-improved-version-pgconfeu-2015-vienna/54561568 PostgreSQL-Consulting@slideshare.net(PostgreSQL-Consulting) Autovacuum, explained for engineers, new improved version PGConf.eu 2015 Vienna PostgreSQL-Consulting How to configure PostgreSQL autovacuum by Ilya Kosmodemiansky <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/pgconfeukosmodemianskyvacuum-151030110722-lva1-app6891-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> How to configure PostgreSQL autovacuum by Ilya Kosmodemiansky
Autovacuum, explained for engineers, new improved version PGConf.eu 2015 Vienna from PostgreSQL-Consulting
]]> 14565 5 https://cdn.slidesharecdn.com/ss_thumbnails/pgconfeukosmodemianskyvacuum-151030110722-lva1-app6891-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Linux tuning to improve PostgreSQL performance /slideshow/linux-tuning-to-improve-postgresql-performance/54529277 pgconfeukosmodemianskylinux-151029151515-lva1-app6891
際際滷s from Linux tuning to improve PostgreSQL performance by Ilya Kosmodemiansky at PGConf.eu 2015 in Viena]]>
際際滷s from Linux tuning to improve PostgreSQL performance by Ilya Kosmodemiansky at PGConf.eu 2015 in Viena]]> Thu, 29 Oct 2015 15:15:15 GMT /slideshow/linux-tuning-to-improve-postgresql-performance/54529277 PostgreSQL-Consulting@slideshare.net(PostgreSQL-Consulting) Linux tuning to improve PostgreSQL performance PostgreSQL-Consulting 際際滷s from Linux tuning to improve PostgreSQL performance by Ilya Kosmodemiansky at PGConf.eu 2015 in Viena <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/pgconfeukosmodemianskylinux-151029151515-lva1-app6891-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> 際際滷s from Linux tuning to improve PostgreSQL performance by Ilya Kosmodemiansky at PGConf.eu 2015 in Viena
Linux tuning to improve PostgreSQL performance from PostgreSQL-Consulting
]]> 36238 11 https://cdn.slidesharecdn.com/ss_thumbnails/pgconfeukosmodemianskylinux-151029151515-lva1-app6891-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 PostgreSQL Meetup Berlin at Zalando HQ /slideshow/postgresql-meetup-berlin-at-zalando-hq/47102972 berlinmeetupkosmodemiansky-150417024453-conversion-gate02
PostgreSQL autovacuum, explained for engineers]]>
PostgreSQL autovacuum, explained for engineers]]> Fri, 17 Apr 2015 02:44:53 GMT /slideshow/postgresql-meetup-berlin-at-zalando-hq/47102972 PostgreSQL-Consulting@slideshare.net(PostgreSQL-Consulting) PostgreSQL Meetup Berlin at Zalando HQ PostgreSQL-Consulting PostgreSQL autovacuum, explained for engineers <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/berlinmeetupkosmodemiansky-150417024453-conversion-gate02-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> PostgreSQL autovacuum, explained for engineers
PostgreSQL Meetup Berlin at Zalando HQ from PostgreSQL-Consulting
]]> 3833 5 https://cdn.slidesharecdn.com/ss_thumbnails/berlinmeetupkosmodemiansky-150417024453-conversion-gate02-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 How does PostgreSQL work with disks: a DBA's checklist in detail. PGConf.US 2015 /slideshow/how-does-postgresql-work-with-disks-a-dbas-checklist-in-detail-pgconfus-2015/46368834 pgconfnykosmodemianskyv1-150327110805-conversion-gate01
]]>
]]> Fri, 27 Mar 2015 11:08:05 GMT /slideshow/how-does-postgresql-work-with-disks-a-dbas-checklist-in-detail-pgconfus-2015/46368834 PostgreSQL-Consulting@slideshare.net(PostgreSQL-Consulting) How does PostgreSQL work with disks: a DBA's checklist in detail. PGConf.US 2015 PostgreSQL-Consulting <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/pgconfnykosmodemianskyv1-150327110805-conversion-gate01-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br>
How does PostgreSQL work with disks: a DBA's checklist in detail. PGConf.US 2015 from PostgreSQL-Consulting
]]> 7833 4 https://cdn.slidesharecdn.com/ss_thumbnails/pgconfnykosmodemianskyv1-150327110805-conversion-gate01-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Pgconfru 2015 kosmodemiansky /slideshow/pgconfru-2015-kosmodemiansky/44489844 pgconfru2015kosmodemiansky-150210045009-conversion-gate01
]]>
]]> Tue, 10 Feb 2015 04:50:08 GMT /slideshow/pgconfru-2015-kosmodemiansky/44489844 PostgreSQL-Consulting@slideshare.net(PostgreSQL-Consulting) Pgconfru 2015 kosmodemiansky PostgreSQL-Consulting <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/pgconfru2015kosmodemiansky-150210045009-conversion-gate01-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br>
Pgconfru 2015 kosmodemiansky from PostgreSQL-Consulting
]]> 1068 2 https://cdn.slidesharecdn.com/ss_thumbnails/pgconfru2015kosmodemiansky-150210045009-conversion-gate01-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 舒从 PostgreSQL 舒弍仂舒亠 亟亳从仂仄 /slideshow/hl-2014-kosmodemiansky/40986570 hl2014kosmodemiansky-141101010749-conversion-gate02
舒从 于 PostgreSQL 仂亠仆仂 于亰舒亳仄仂亟亠亶于亳亠 亟亳从仂仄, 从舒从亳亠 仗仂弍仍亠仄 仗仂亳亰于仂亟亳亠仍仆仂亳 仗亳 仂仄 弍于舒ﾑ 亳 从舒从 亳 亠舒 于弍仂仂仄 仗仂亟仂亟亠亞仂 hardware, 仆舒仂亶从舒仄亳 仂仗亠舒亳仂仆仆仂亶 亳亠仄 亳 仆舒仂亶从舒仄亳 PostgreSQL]]>
舒从 于 PostgreSQL 仂亠仆仂 于亰舒亳仄仂亟亠亶于亳亠 亟亳从仂仄, 从舒从亳亠 仗仂弍仍亠仄 仗仂亳亰于仂亟亳亠仍仆仂亳 仗亳 仂仄 弍于舒ﾑ 亳 从舒从 亳 亠舒 于弍仂仂仄 仗仂亟仂亟亠亞仂 hardware, 仆舒仂亶从舒仄亳 仂仗亠舒亳仂仆仆仂亶 亳亠仄 亳 仆舒仂亶从舒仄亳 PostgreSQL]]> Sat, 01 Nov 2014 01:07:49 GMT /slideshow/hl-2014-kosmodemiansky/40986570 PostgreSQL-Consulting@slideshare.net(PostgreSQL-Consulting) 舒从 PostgreSQL 舒弍仂舒亠 亟亳从仂仄 PostgreSQL-Consulting 舒从 于 PostgreSQL 仂亠仆仂 于亰舒亳仄仂亟亠亶于亳亠 亟亳从仂仄, 从舒从亳亠 仗仂弍仍亠仄 仗仂亳亰于仂亟亳亠仍仆仂亳 仗亳 仂仄 弍于舒ﾑ 亳 从舒从 亳 亠舒 于弍仂仂仄 仗仂亟仂亟亠亞仂 hardware, 仆舒仂亶从舒仄亳 仂仗亠舒亳仂仆仆仂亶 亳亠仄 亳 仆舒仂亶从舒仄亳 PostgreSQL <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/hl2014kosmodemiansky-141101010749-conversion-gate02-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> 舒从 于 PostgreSQL 仂亠仆仂 于亰舒亳仄仂亟亠亶于亳亠 亟亳从仂仄, 从舒从亳亠 仗仂弍仍亠仄 仗仂亳亰于仂亟亳亠仍仆仂亳 仗亳 仂仄 弍于舒ﾑ 亳 从舒从 亳 亠舒 于弍仂仂仄 仗仂亟仂亟亠亞仂 hardware, 仆舒仂亶从舒仄亳 仂仗亠舒亳仂仆仆仂亶 亳亠仄 亳 仆舒仂亶从舒仄亳 PostgreSQL
舒从 PostgreSQL 舒弍仂舒亠 亟亳从仂仄 from PostgreSQL-Consulting
]]> 1960 1 https://cdn.slidesharecdn.com/ss_thumbnails/hl2014kosmodemiansky-141101010749-conversion-gate02-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Kosmodemiansky wr 2013 /slideshow/kosmodemiansky-wr-2013/27163987 kosmodemianskywr2013-131014044712-phpapp01
]]>
]]> Mon, 14 Oct 2013 04:47:12 GMT /slideshow/kosmodemiansky-wr-2013/27163987 PostgreSQL-Consulting@slideshare.net(PostgreSQL-Consulting) Kosmodemiansky wr 2013 PostgreSQL-Consulting <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/kosmodemianskywr2013-131014044712-phpapp01-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br>
Kosmodemiansky wr 2013 from PostgreSQL-Consulting
]]> 583 3 https://cdn.slidesharecdn.com/ss_thumbnails/kosmodemianskywr2013-131014044712-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 舒从亳仄 仂亞从. Postgres-XC /slideshow/postgresxc/14927427 postgresql-xc-121029001633-phpapp02
仂从仍舒亟 仆舒 PGDay 于 舒仄从舒 从仂仆亠亠仆亳亳 Highload]]>
仂从仍舒亟 仆舒 PGDay 于 舒仄从舒 从仂仆亠亠仆亳亳 Highload]]> Mon, 29 Oct 2012 00:16:31 GMT /slideshow/postgresxc/14927427 PostgreSQL-Consulting@slideshare.net(PostgreSQL-Consulting) 舒从亳仄 仂亞从. Postgres-XC PostgreSQL-Consulting 仂从仍舒亟 仆舒 PGDay 于 舒仄从舒 从仂仆亠亠仆亳亳 Highload <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/postgresql-xc-121029001633-phpapp02-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> 仂从仍舒亟 仆舒 PGDay 于 舒仄从舒 从仂仆亠亠仆亳亳 Highload
舒从亳仄 仂亞从. Postgres-XC from PostgreSQL-Consulting
]]> 1100 2 https://cdn.slidesharecdn.com/ss_thumbnails/postgresql-xc-121029001633-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 于舒仆 个仂仍从仂于. Tricky SQL /slideshow/ivan-frolkov-tricky-sql/14927403 frolkov-2012-121029001054-phpapp01
仂从仍舒亟 仆舒 PGDay 于 舒仄从舒 从仂仆亠亠仆亳亳 Highload]]>
仂从仍舒亟 仆舒 PGDay 于 舒仄从舒 从仂仆亠亠仆亳亳 Highload]]> Mon, 29 Oct 2012 00:10:53 GMT /slideshow/ivan-frolkov-tricky-sql/14927403 PostgreSQL-Consulting@slideshare.net(PostgreSQL-Consulting) 于舒仆 个仂仍从仂于. Tricky SQL PostgreSQL-Consulting 仂从仍舒亟 仆舒 PGDay 于 舒仄从舒 从仂仆亠亠仆亳亳 Highload <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/frolkov-2012-121029001054-phpapp01-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> 仂从仍舒亟 仆舒 PGDay 于 舒仄从舒 从仂仆亠亠仆亳亳 Highload
于舒仆 个仂仍从仂于. Tricky SQL from PostgreSQL-Consulting
]]> 1272 3 https://cdn.slidesharecdn.com/ss_thumbnails/frolkov-2012-121029001054-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 仍 仂仄仂亟亠仄礌从亳亶. 仗仂仍亰仂于舒仆亳亠 仂亠亠亟亠亶 舒亳仆仂仆仆 仂仂弍亠仆亳亶 PostgreSQL /slideshow/kosmodemiansky-2012/14927372 kosmodemiansky2012-121029000545-phpapp01
仂从仍舒亟 仆舒 PGDay 于 舒仄从舒 从仂仆亠亠仆亳亳 Highload]]>
仂从仍舒亟 仆舒 PGDay 于 舒仄从舒 从仂仆亠亠仆亳亳 Highload]]> Mon, 29 Oct 2012 00:05:43 GMT /slideshow/kosmodemiansky-2012/14927372 PostgreSQL-Consulting@slideshare.net(PostgreSQL-Consulting) 仍 仂仄仂亟亠仄礌从亳亶. 仗仂仍亰仂于舒仆亳亠 仂亠亠亟亠亶 舒亳仆仂仆仆 仂仂弍亠仆亳亶 PostgreSQL PostgreSQL-Consulting 仂从仍舒亟 仆舒 PGDay 于 舒仄从舒 从仂仆亠亠仆亳亳 Highload <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/kosmodemiansky2012-121029000545-phpapp01-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> 仂从仍舒亟 仆舒 PGDay 于 舒仄从舒 从仂仆亠亠仆亳亳 Highload
仍 仂仄仂亟亠仄礌从亳亶. 仗仂仍亰仂于舒仆亳亠 仂亠亠亟亠亶 舒亳仆仂仆仆 仂仂弍亠仆亳亶 PostgreSQL from PostgreSQL-Consulting
]]> 799 3 https://cdn.slidesharecdn.com/ss_thumbnails/kosmodemiansky2012-121029000545-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 https://cdn.slidesharecdn.com/profile-photo-PostgreSQL-Consulting-48x48.jpg?cb=1529416867 www.dataegret.com/ https://cdn.slidesharecdn.com/ss_thumbnails/kosmodemianskyupgrades-171026085144-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/ilya-kosmodemiansky-an-ultimate-guide-to-upgrading-your-postgresql-installation-pgconfeu/81232750 Ilya Kosmodemiansky - ... https://cdn.slidesharecdn.com/ss_thumbnails/scale2017kosmodemiansky-170331191144-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/linux-io-internals-for-database-administrators-scale-2017-and-pgday-nordic-2017-version/74095743 Linux IO internals for... https://cdn.slidesharecdn.com/ss_thumbnails/pgconfus2017kosmodemiansky-170331190504-thumbnail.jpg?width=320&height=320&fit=bounds PostgreSQL-Consulting/postgresql-worst-practices-version-pgconfus-2017-by-ilya-kosmodemiansky PostgreSQL worst pract...