3.69 score from hupso.pl for:
depesz.com



HTML Content


Titleselect * from depesz;

Length: 23, Words: 3
Description pusty

Length: 0, Words: 0
Keywords pusty
Robots
Charset UTF-8
Og Meta - Title pusty
Og Meta - Description pusty
Og Meta - Site name pusty
Tytuł powinien zawierać pomiędzy 10 a 70 znaków (ze spacjami), a mniej niż 12 słów w długości.
Meta opis powinien zawierać pomiędzy 50 a 160 znaków (łącznie ze spacjami), a mniej niż 24 słów w długości.
Kodowanie znaków powinny być określone , UTF-8 jest chyba najlepszy zestaw znaków, aby przejść z powodu UTF-8 jest bardziej międzynarodowy kodowaniem.
Otwarte obiekty wykresu powinny być obecne w stronie internetowej (więcej informacji na temat protokołu OpenGraph: http://ogp.me/)

SEO Content

Words/Characters 1924
Text/HTML 36.94 %
Headings H1 0
H2 5
H3 0
H4 0
H5 0
H6 0
H1
H2
search
follow me
popular posts
postgresql
about me
H3
H4
H5
H6
strong
b
i
em
Bolds strong 0
b 0
i 0
em 0
Zawartość strony internetowej powinno zawierać więcej niż 250 słów, z stopa tekst / kod jest wyższy niż 20%.
Pozycji używać znaczników (h1, h2, h3, ...), aby określić temat sekcji lub ustępów na stronie, ale zwykle, użyj mniej niż 6 dla każdego tagu pozycje zachować swoją stronę zwięzły.
Styl używać silnych i kursywy znaczniki podkreślić swoje słowa kluczowe swojej stronie, ale nie nadużywać (mniej niż 16 silnych tagi i 16 znaczników kursywy)

Statystyki strony

twitter:title pusty
twitter:description pusty
google+ itemprop=name pusty
Pliki zewnętrzne 8
Pliki CSS 3
Pliki javascript 5
Plik należy zmniejszyć całkowite odwołanie plików (CSS + JavaScript) do 7-8 maksymalnie.

Linki wewnętrzne i zewnętrzne

Linki 122
Linki wewnętrzne 2
Linki zewnętrzne 120
Linki bez atrybutu Title 101
Linki z atrybutem NOFOLLOW 0
Linki - Użyj atrybutu tytuł dla każdego łącza. Nofollow link jest link, który nie pozwala wyszukiwarkom boty zrealizują są odnośniki no follow. Należy zwracać uwagę na ich użytkowania

Linki wewnętrzne

irc irc://irc.freenode.net/%23postgresql,ischannel
irc help channel irc://irc.freenode.net/#postgresql

Linki zewnętrzne

blog https://www.depesz.com
movies https://www.depesz.com/movies/
projects https://www.depesz.com/projects/
contact https://www.depesz.com/contact/
getting first and last values per group https://www.depesz.com/2017/02/20/getting-first-and-last-values-per-group/
aggregate https://www.depesz.com/tag/aggregate/
extension https://www.depesz.com/tag/extension/
first https://www.depesz.com/tag/first/
first_last https://www.depesz.com/tag/first_last/
github https://www.depesz.com/tag/github/
last https://www.depesz.com/tag/last/
pgxn https://www.depesz.com/tag/pgxn/
postgresql https://www.depesz.com/tag/postgresql/
2 comments » https://www.depesz.com/2017/02/20/getting-first-and-last-values-per-group/#comments
recursive queries https://www.depesz.com/2012/10/05/getting-top-n-rows-per-group/
read more » https://www.depesz.com/2017/02/20/getting-first-and-last-values-per-group/#more-3225
why does “sudo ls -l /proc/1/fd/*” fail? https://www.depesz.com/2017/02/20/why-does-sudo-ls-l-proc1fd-fail/
bash https://www.depesz.com/tag/bash/
glob https://www.depesz.com/tag/glob/
gotcha https://www.depesz.com/tag/gotcha/
pitfall https://www.depesz.com/tag/pitfall/
shell https://www.depesz.com/tag/shell/
sudo https://www.depesz.com/tag/sudo/
1 comment » https://www.depesz.com/2017/02/20/why-does-sudo-ls-l-proc1fd-fail/#comments
read more » https://www.depesz.com/2017/02/20/why-does-sudo-ls-l-proc1fd-fail/#more-3222
waiting for postgresql 10 – logical replication https://www.depesz.com/2017/02/07/waiting-for-postgresql-10-logical-replication/
logical https://www.depesz.com/tag/logical/
pg10 https://www.depesz.com/tag/pg10/
postgresql https://www.depesz.com/tag/postgresql/
replication https://www.depesz.com/tag/replication/
upgrade https://www.depesz.com/tag/upgrade/
6 comments » https://www.depesz.com/2017/02/07/waiting-for-postgresql-10-logical-replication/#comments
committed http://git.postgresql.org/pg/commitdiff/665d1fad99e7b11678b0d5fa24d2898424243cd6
read more » https://www.depesz.com/2017/02/07/waiting-for-postgresql-10-logical-replication/#more-3210
waiting for postgresql 10 – add pg_sequence system catalog https://www.depesz.com/2017/02/06/waiting-for-postgresql-10-add-pg_sequence-system-catalog/
pg10 https://www.depesz.com/tag/pg10/
pg_sequence https://www.depesz.com/tag/pg_sequence/
postgresql https://www.depesz.com/tag/postgresql/
sequence https://www.depesz.com/tag/sequence/
sequences https://www.depesz.com/tag/sequences/
4 comments » https://www.depesz.com/2017/02/06/waiting-for-postgresql-10-add-pg_sequence-system-catalog/#comments
committed http://git.postgresql.org/pg/commitdiff/1753b1b027035029c2a2a1649065762fafbf63f3
read more » https://www.depesz.com/2017/02/06/waiting-for-postgresql-10-add-pg_sequence-system-catalog/#more-3208
generate short, random, textual ids https://www.depesz.com/2017/02/06/generate-short-random-textual-ids/
extension https://www.depesz.com/tag/extension/
github https://www.depesz.com/tag/github/
pgxn https://www.depesz.com/tag/pgxn/
postgresql https://www.depesz.com/tag/postgresql/
primary key https://www.depesz.com/tag/primary-key/
random https://www.depesz.com/tag/random/
short_ids https://www.depesz.com/tag/short_ids/
1 comment » https://www.depesz.com/2017/02/06/generate-short-random-textual-ids/#comments
explain.depesz.com https://explain.depesz.com/
sources https://github.com/depesz/explain.depesz.com/blob/master/sql/create.sql
read more » https://www.depesz.com/2017/02/06/generate-short-random-textual-ids/#more-3212
waiting for postgresql 10 – implement table partitioning. https://www.depesz.com/2017/02/06/waiting-for-postgresql-10-implement-table-partitioning/
benchmark https://www.depesz.com/tag/benchmark/
partitioning https://www.depesz.com/tag/partitioning/
partitions https://www.depesz.com/tag/partitions/
pg10 https://www.depesz.com/tag/pg10/
postgresql https://www.depesz.com/tag/postgresql/
triggers https://www.depesz.com/tag/triggers/
6 comments » https://www.depesz.com/2017/02/06/waiting-for-postgresql-10-implement-table-partitioning/#comments
committed http://git.postgresql.org/pg/commitdiff/f0e44751d7175fa3394da2c8f85e3ceb3cdbfe63
read more » https://www.depesz.com/2017/02/06/waiting-for-postgresql-10-implement-table-partitioning/#more-3206
major-version upgrading with minimal downtime https://www.depesz.com/2016/11/08/major-version-upgrading-with-minimal-downtime/
logical https://www.depesz.com/tag/logical/
major https://www.depesz.com/tag/major/
pglogical https://www.depesz.com/tag/pglogical/
postgresql https://www.depesz.com/tag/postgresql/
replication https://www.depesz.com/tag/replication/
upgrade https://www.depesz.com/tag/upgrade/
7 comments » https://www.depesz.com/2016/11/08/major-version-upgrading-with-minimal-downtime/#comments
read more » https://www.depesz.com/2016/11/08/major-version-upgrading-with-minimal-downtime/#more-3186
waiting for postgresql 10 – postgres_fdw: push down aggregates to remote servers. https://www.depesz.com/2016/10/25/waiting-for-postgresql-10-postgres_fdw-push-down-aggregates-to-remote-servers/
aggregate https://www.depesz.com/tag/aggregate/
fdw https://www.depesz.com/tag/fdw/
pg10 https://www.depesz.com/tag/pg10/
postgresql https://www.depesz.com/tag/postgresql/
postgres_fdw https://www.depesz.com/tag/postgres_fdw/
8 comments » https://www.depesz.com/2016/10/25/waiting-for-postgresql-10-postgres_fdw-push-down-aggregates-to-remote-servers/#comments
committed http://git.postgresql.org/pg/commitdiff/7012b132d07c2b4ea15b0b3cb1ea9f3278801d98
read more » https://www.depesz.com/2016/10/25/waiting-for-postgresql-10-postgres_fdw-push-down-aggregates-to-remote-servers/#more-3182
waiting for postgresql 10 – rename “pg_xlog” directory to “pg_wal”. https://www.depesz.com/2016/10/25/waiting-for-postgresql-10-rename-pg_xlog-directory-to-pg_wal/
backup https://www.depesz.com/tag/backup/
pg10 https://www.depesz.com/tag/pg10/
pg_basebackup https://www.depesz.com/tag/pg_basebackup/
pg_wal https://www.depesz.com/tag/pg_wal/
pg_xlog https://www.depesz.com/tag/pg_xlog/
postgresql https://www.depesz.com/tag/postgresql/
wal https://www.depesz.com/tag/wal/
1 comment » https://www.depesz.com/2016/10/25/waiting-for-postgresql-10-rename-pg_xlog-directory-to-pg_wal/#comments
committed http://git.postgresql.org/pg/commitdiff/f82ec32ac30ae7e3ec7c84067192535b2ff8ec0e
discussion link https://www.postgresql.org/message-id/cab7npqtec-8+zux8_-4zd46v7ypwooefxgndfsq5rg8iblvm1a@mail.gmail.com
read more » https://www.depesz.com/2016/10/25/waiting-for-postgresql-10-rename-pg_xlog-directory-to-pg_wal/#more-3178
missing waiting for …. ? https://www.depesz.com/2016/09/26/missing-waiting-for/
postgresql https://www.depesz.com/tag/postgresql/
no comments » https://www.depesz.com/2016/09/26/missing-waiting-for/#respond
comments rss http://www.depesz.com/comments/feed/
posts rss http://depesz.com/feed/
getting first and last values per group https://www.depesz.com/2017/02/20/getting-first-and-last-values-per-group/
char(x) vs. varchar(x) vs. varchar vs. text – updated 2010-03-03 https://www.depesz.com/2010/03/02/charx-vs-varcharx-vs-varchar-vs-text/
how much ram is postgresql using? https://www.depesz.com/2012/06/09/how-much-ram-is-postgresql-using/
why is upsert so complicated? https://www.depesz.com/2012/06/10/why-is-upsert-so-complicated/
explaining the unexplainable – part 3 https://www.depesz.com/2013/05/09/explaining-the-unexplainable-part-3/
how i learned to stop worrying and love the triggers https://www.depesz.com/2012/11/14/how-i-learned-to-stop-worrying-and-love-the-triggers/
waiting for 9.6 – add if not exists processing to alter table add column https://www.depesz.com/2015/08/19/waiting-for-9-6-add-if-not-exists-processing-to-alter-table-add-column/
why does “sudo ls -l /proc/1/fd/*” fail? https://www.depesz.com/2017/02/20/why-does-sudo-ls-l-proc1fd-fail/
understanding postgresql.conf : log* https://www.depesz.com/2011/05/06/understanding-postgresql-conf-log/
waiting for postgresql 10 – logical replication https://www.depesz.com/2017/02/07/waiting-for-postgresql-10-logical-replication/
documentation http://www.postgresql.org/docs/current/interactive/index.html
explain analyze analyzer http://explain.depesz.com/
mailing lists search http://archives.postgresql.org/
pg planet http://planet.postgresql.org/
postgresql home page http://www.postgresql.org/
cpan http://search.cpan.org/~depesz/
github https://github.com/depesz/
linked in http://linkedin.com/in/depesz
twitter https://twitter.com/the_depesz
prev https://www.depesz.com/page/2/

Zdjęcia

Zdjęcia 0
Zdjęcia bez atrybutu ALT 0
Zdjęcia bez atrybutu TITLE 0
Korzystanie Obraz ALT i TITLE atrybutu dla każdego obrazu.

Zdjęcia bez atrybutu TITLE

empty

Zdjęcia bez atrybutu ALT

empty

Ranking:


Alexa Traffic
Daily Global Rank Trend
Daily Reach (Percent)









Majestic SEO











Text on page:

blog movies projects contact getting first and last values per group february 20th, 2017 by depesz | tags: aggregate, extension, first, first_last, github, last, pgxn, postgresql | 2 comments » every so often someone needs solution to getting first (or couple of first) values for given column. or last. for some cases (when there is not many groups) you can use recursive queries. but it's not always the best choice. let's try to implement first() and last() aggregates, so these could be easily used by anybody. read more » why does “sudo ls -l /proc/1/fd/*” fail? february 20th, 2017 by depesz | tags: bash, glob, gotcha, pitfall, shell, sudo | 1 comment » i usually write about postgresql, but lately someone asked for help, and one of the problems was similar to sudo command from title. this was not the first time i saw it, so figured, i'll write a blogpost about it, just so i can refer people to it in the future. read more » waiting for postgresql 10 – logical replication february 7th, 2017 by depesz | tags: logical, pg10, postgresql, replication, upgrade | 6 comments » on 20th of january, peter eisentraut committed patch: logical replication - add publication catalogs and ddl - add subscription catalog and ddl - define logical replication protocol and output plugin - add logical replication workers from: petr jelinek reviewed-by: steve singer reviewed-by: andres freund reviewed-by: erik rijkers reviewed-by: peter eisentrautlogical replication - add publication catalogs and ddl - add subscription catalog and ddl - define logical replication protocol and output plugin - add logical replication workers from: petr jelinek reviewed-by: steve singer reviewed-by: andres freund reviewed-by: erik rijkers reviewed-by: peter eisentraut read more » waiting for postgresql 10 – add pg_sequence system catalog february 6th, 2017 by depesz | tags: pg10, pg_sequence, postgresql, sequence, sequences | 4 comments » on 20th of december, peter eisentraut committed patch: add pg_sequence system catalog move sequence metadata (start, increment, etc.) into a proper system catalog instead of storing it in the sequence heap object. this separates the metadata from the sequence data. sequence metadata is now operated on transactionally by ddl commands, whereas previously rollbacks of sequence-related ddl commands would be ignored. reviewed-by: andreas karlssonadd pg_sequence system catalog move sequence metadata (start, increment, etc.) into a proper system catalog instead of storing it in the sequence heap object. this separates the metadata from the sequence data. sequence metadata is now operated on transactionally by ddl commands, whereas previously rollbacks of sequence-related ddl commands would be ignored. reviewed-by: andreas karlsson read more » generate short, random, textual ids february 6th, 2017 by depesz | tags: extension, github, pgxn, postgresql, primary key, random, short_ids | 1 comment » couple of people asked, on irc, about how to generate unique, short, ids for rows. since i wrote code for this for explain.depesz.com, i figured that instead of pointing to sources, and letting everyone to extract the functions, i will, instead, write a set of functions that what is needed in reusable way. read more » waiting for postgresql 10 – implement table partitioning. february 6th, 2017 by depesz | tags: benchmark, partitioning, partitions, pg10, postgresql, triggers | 6 comments » i had two month delay related to some work, but now i can finally write about: on 7th of december, robert haas committed patch: implement table partitioning. table partitioning is like table inheritance and reuses much of the existing infrastructure, but there are some important differences. the parent is called a partitioned table and is always empty; it may not have indexes or non-inherited constraints, since those make no sense for a relation with no data of its own. the children are called partitions and contain all of the actual data. each partition has an implicit partitioning constraint. multiple inheritance is not allowed, and partitioning and inheritance can't be mixed. partitions can't have extra columns and may not allow nulls unless the parent does. tuples inserted into the parent are automatically routed to the correct partition, so tuple-routing on insert triggers are not needed. tuple routing isn't yet supported for partitions which are foreign tables, and it doesn't handle updates that cross partition boundaries. currently, tables can be range-partitioned or list-partitioned. list partitioning is limited to a single column, but range partitioning can involve multiple columns. a partitioning "column" can be an expression. because table partitioning is less general than table inheritance, it is hoped that it will be easier to reason about properties of partitions, and therefore that this will serve as a better foundation for a variety of possible optimizations, including query planner optimizations. the tuple routing based which this patch does based on the implicit partitioning constraints is an example of this, but it seems likely that many other useful optimizations are also possible. amit langote, reviewed and tested by robert haas, ashutosh bapat, amit kapila, rajkumar raghuwanshi, corey huinker, jaime casanova, rushabh lathia, erik rijkers, among others. minor revisions by me.implement table partitioning. table partitioning is like table inheritance and reuses much of the existing infrastructure, but there are some important differences. the parent is called a partitioned table and is always empty; it may not have indexes or non-inherited constraints, since those make no sense for a relation with no data of its own. the children are called partitions and contain all of the actual data. each partition has an implicit partitioning constraint. multiple inheritance is not allowed, and partitioning and inheritance can't be mixed. partitions can't have extra columns and may not allow nulls unless the parent does. tuples inserted into the parent are automatically routed to the correct partition, so tuple-routing on insert triggers are not needed. tuple routing isn't yet supported for partitions which are foreign tables, and it doesn't handle updates that cross partition boundaries. currently, tables can be range-partitioned or list-partitioned. list partitioning is limited to a single column, but range partitioning can involve multiple columns. a partitioning "column" can be an expression. because table partitioning is less general than table inheritance, it is hoped that it will be easier to reason about properties of partitions, and therefore that this will serve as a better foundation for a variety of possible optimizations, including query planner optimizations. the tuple routing based which this patch does based on the implicit partitioning constraints is an example of this, but it seems likely that many other useful optimizations are also possible. amit langote, reviewed and tested by robert haas, ashutosh bapat, amit kapila, rajkumar raghuwanshi, corey huinker, jaime casanova, rushabh lathia, erik rijkers, among others. minor revisions by me. read more » major-version upgrading with minimal downtime november 8th, 2016 by depesz | tags: logical, major, pglogical, postgresql, replication, upgrade | 7 comments » there is this idea that from 9.5 we will be able to upgrade pg clusters to newer, major, version, without downtime (well, almost), thanks to magic of logical replication. sounds very promising, so i figured – i'll test it. to some extent at least. read more » waiting for postgresql 10 – postgres_fdw: push down aggregates to remote servers. october 25th, 2016 by depesz | tags: aggregate, fdw, pg10, postgresql, postgres_fdw | 8 comments » on 21st of october, robert haas committed patch: postgres_fdw: push down aggregates to remote servers. now that the upper planner uses paths, and now that we have proper hooks to inject paths into the upper planning process, it's possible for foreign data wrappers to arrange to push aggregates to the remote side instead of fetching all of the rows and aggregating them locally. this figures to be a massive win for performance, so teach postgres_fdw to do it. jeevan chalke and ashutosh bapat. reviewed by ashutosh bapat with additional testing by prabhat sahu. various mostly cosmetic changes by me.postgres_fdw: push down aggregates to remote servers. now that the upper planner uses paths, and now that we have proper hooks to inject paths into the upper planning process, it's possible for foreign data wrappers to arrange to push aggregates to the remote side instead of fetching all of the rows and aggregating them locally. this figures to be a massive win for performance, so teach postgres_fdw to do it. jeevan chalke and ashutosh bapat. reviewed by ashutosh bapat with additional testing by prabhat sahu. various mostly cosmetic changes by me. read more » waiting for postgresql 10 – rename “pg_xlog” directory to “pg_wal”. october 25th, 2016 by depesz | tags: backup, pg10, pg_basebackup, pg_wal, pg_xlog, postgresql, wal | 1 comment » on 20th of october, robert haas committed patch: rename "pg_xlog" directory to "pg_wal". "xlog" is not a particularly clear abbreviation for "write-ahead log", and it sometimes confuses users into believe that the contents of the "pg_xlog" directory are not critical data, leading to unpleasant consequences. so, rename the directory to "pg_wal". this patch modifies pg_upgrade and pg_basebackup to understand both the old and new directory layouts; the former is necessary given the purpose of the tool, while the latter merely avoids an unnecessary backward-compatibility break. we may wish to consider renaming other programs, switches, and functions which still use the old "xlog" naming to also refer to "wal". however, that's still under discussion, so let's do just this much for now. discussion: cab7npqtec-8+zux8_-4zd46v7ypwooefxgndfsq5rg8iblvm1a@mail.gmail.com michael paquierrename "pg_xlog" directory to "pg_wal". "xlog" is not a particularly clear abbreviation for "write-ahead log", and it sometimes confuses users into believe that the contents of the "pg_xlog" directory are not critical data, leading to unpleasant consequences. so, rename the directory to "pg_wal". this patch modifies pg_upgrade and pg_basebackup to understand both the old and new directory layouts; the former is necessary given the purpose of the tool, while the latter merely avoids an unnecessary backward-compatibility break. we may wish to consider renaming other programs, switches, and functions which still use the old "xlog" naming to also refer to "wal". however, that's still under discussion, so let's do just this much for now. discussion: cab7npqtec-8+zux8_-4zd46v7ypwooefxgndfsq5rg8iblvm1a@mail.gmail.com michael paquier discussion link read more » missing waiting for …. ? september 26th, 2016 by depesz | tags: postgresql | no comments » it looks that for some reason my subscription to pgsql-committers disappeared, and i stopped receiving mails from this list. i also didn't notice it, for some time – not sure when it got lost. i did resubscribed now, but if you can think of any specific commits that i should have written about, but haven't, please let me know, and i'll write about it. sorry for the problem. search follow me comments rss posts rss popular posts getting first and last values per group 757 views | 2 comments char(x) vs. varchar(x) vs. varchar vs. text – updated 2010-03-03 237 views | 0 comments how much ram is postgresql using? 200 views | 0 comments why is upsert so complicated? 198 views | 0 comments explaining the unexplainable – part 3 190 views | 0 comments how i learned to stop worrying and love the triggers 177 views | 0 comments waiting for 9.6 – add if not exists processing to alter table add column 161 views | 0 comments why does “sudo ls -l /proc/1/fd/*” fail? 160 views | 1 comment understanding postgresql.conf : log* 151 views | 0 comments waiting for postgresql 10 – logical replication 144 views | 0 comments postgresql documentation explain analyze analyzer irc help channel mailing lists search pg planet postgresql home page about me cpan github linked in twitter prev


Here you find all texts from your page as Google (googlebot) and others search engines seen it.

Words density analysis:

Numbers of all words: 1909

One word

Two words phrases

Three words phrases

the - 3.82% (73)
and - 3.25% (62)
part - 2.3% (44)
partition - 2.15% (41)
for - 2.15% (41)
that - 1.1% (21)
all - 1.1% (21)
comment - 1.1% (21)
are - 1.1% (21)
able - 1.1% (21)
postgresql - 1.05% (20)
partitioning - 1.05% (20)
table - 0.94% (18)
this - 0.94% (18)
per - 0.94% (18)
not - 0.94% (18)
sequence - 0.94% (18)
comments - 0.89% (17)
data - 0.84% (16)
use - 0.84% (16)
can - 0.73% (14)
reviewed - 0.73% (14)
add - 0.68% (13)
logical - 0.63% (12)
now - 0.58% (11)
depesz - 0.58% (11)
some - 0.58% (11)
- 0.58% (11)
but - 0.58% (11)
replication - 0.58% (11)
reviewed-by: - 0.52% (10)
one - 0.52% (10)
views - 0.52% (10)
column - 0.52% (10)
tags: - 0.52% (10)
about - 0.47% (9)
catalog - 0.47% (9)
wal - 0.47% (9)
directory - 0.47% (9)
more - 0.47% (9)
read - 0.47% (9)
patch - 0.47% (9)
partitions - 0.47% (9)
postgresql, - 0.42% (8)
first - 0.42% (8)
waiting - 0.42% (8)
ddl - 0.42% (8)
into - 0.42% (8)
have - 0.42% (8)
does - 0.42% (8)
tuple - 0.42% (8)
inheritance - 0.42% (8)
from - 0.37% (7)
write - 0.37% (7)
ashutosh - 0.31% (6)
which - 0.31% (6)
will - 0.31% (6)
instead - 0.31% (6)
uses - 0.31% (6)
proper - 0.31% (6)
postgres_fdw - 0.31% (6)
range - 0.31% (6)
other - 0.31% (6)
optimizations - 0.31% (6)
routing - 0.31% (6)
aggregates - 0.31% (6)
metadata - 0.31% (6)
list - 0.31% (6)
may - 0.31% (6)
possible - 0.31% (6)
last - 0.31% (6)
with - 0.31% (6)
partitioned - 0.31% (6)
february - 0.31% (6)
2017 - 0.31% (6)
parent - 0.31% (6)
bapat - 0.31% (6)
time - 0.31% (6)
there - 0.31% (6)
under - 0.26% (5)
system - 0.26% (5)
much - 0.26% (5)
also - 0.26% (5)
discussion - 0.26% (5)
any - 0.26% (5)
let - 0.26% (5)
20th - 0.26% (5)
serve - 0.26% (5)
haas - 0.26% (5)
upgrade - 0.26% (5)
test - 0.26% (5)
down - 0.26% (5)
pg10, - 0.26% (5)
committed - 0.26% (5)
patch: - 0.26% (5)
rename - 0.26% (5)
command - 0.26% (5)
remote - 0.26% (5)
robert - 0.26% (5)
how - 0.26% (5)
ids - 0.26% (5)
push - 0.26% (5)
commands - 0.21% (4)
can't - 0.21% (4)
functions - 0.21% (4)
implicit - 0.21% (4)
less - 0.21% (4)
like - 0.21% (4)
called - 0.21% (4)
multiple - 0.21% (4)
columns - 0.21% (4)
each - 0.21% (4)
tables - 0.21% (4)
insert - 0.21% (4)
triggers - 0.21% (4)
allow - 0.21% (4)
foreign - 0.21% (4)
data. - 0.21% (4)
old - 0.21% (4)
planner - 0.21% (4)
side - 0.21% (4)
"pg_xlog" - 0.21% (4)
"pg_wal". - 0.21% (4)
sudo - 0.21% (4)
"xlog" - 0.21% (4)
implement - 0.21% (4)
eisentraut - 0.21% (4)
necessary - 0.21% (4)
still - 0.21% (4)
you - 0.21% (4)
naming - 0.21% (4)
got - 0.21% (4)
explain - 0.21% (4)
peter - 0.21% (4)
paths - 0.21% (4)
upper - 0.21% (4)
rijkers - 0.21% (4)
based - 0.21% (4)
constraints - 0.21% (4)
amit - 0.21% (4)
me. - 0.21% (4)
6th, - 0.21% (4)
pg_sequence - 0.21% (4)
erik - 0.21% (4)
2016 - 0.21% (4)
it. - 0.21% (4)
october - 0.21% (4)
pg_basebackup - 0.16% (3)
understand - 0.16% (3)
servers. - 0.16% (3)
rows - 0.16% (3)
new - 0.16% (3)
very - 0.16% (3)
getting - 0.16% (3)
extra - 0.16% (3)
than - 0.16% (3)
its - 0.16% (3)
postgres_fdw: - 0.16% (3)
vs. - 0.16% (3)
ram - 0.16% (3)
reason - 0.16% (3)
github - 0.16% (3)
prev - 0.16% (3)
it's - 0.16% (3)
always - 0.16% (3)
refer - 0.16% (3)
given - 0.16% (3)
sequences - 0.16% (3)
just - 0.16% (3)
i'll - 0.16% (3)
it, - 0.16% (3)
since - 0.16% (3)
figured - 0.16% (3)
needed - 0.16% (3)
partitioning. - 0.16% (3)
many - 0.16% (3)
related - 0.16% (3)
logical, - 0.16% (3)
partitions, - 0.16% (3)
group - 0.16% (3)
values - 0.16% (3)
let's - 0.16% (3)
why - 0.16% (3)
subscription - 0.16% (3)
clear - 0.1% (2)
contents - 0.1% (2)
prabhat - 0.1% (2)
sahu. - 0.1% (2)
various - 0.1% (2)
believe - 0.1% (2)
mostly - 0.1% (2)
cosmetic - 0.1% (2)
changes - 0.1% (2)
backup, - 0.1% (2)
particularly - 0.1% (2)
users - 0.1% (2)
confuses - 0.1% (2)
sometimes - 0.1% (2)
log", - 0.1% (2)
was - 0.1% (2)
"write-ahead - 0.1% (2)
asked - 0.1% (2)
fail? - 0.1% (2)
abbreviation - 0.1% (2)
indexes - 0.1% (2)
jeevan - 0.1% (2)
testing - 0.1% (2)
arrange - 0.1% (2)
define - 0.1% (2)
25th, - 0.1% (2)
october, - 0.1% (2)
catalogs - 0.1% (2)
publication - 0.1% (2)
paths, - 0.1% (2)
hooks - 0.1% (2)
inject - 0.1% (2)
replication, - 0.1% (2)
planning - 0.1% (2)
process, - 0.1% (2)
wrappers - 0.1% (2)
fetching - 0.1% (2)
additional - 0.1% (2)
people - 0.1% (2)
aggregating - 0.1% (2)
them - 0.1% (2)
locally. - 0.1% (2)
figures - 0.1% (2)
massive - 0.1% (2)
win - 0.1% (2)
performance, - 0.1% (2)
teach - 0.1% (2)
data, - 0.1% (2)
chalke - 0.1% (2)
bapat. - 0.1% (2)
critical - 0.1% (2)
“sudo - 0.1% (2)
leading - 0.1% (2)
rss - 0.1% (2)
michael - 0.1% (2)
paquier - 0.1% (2)
couple - 0.1% (2)
link - 0.1% (2)
when - 0.1% (2)
someone - 0.1% (2)
did - 0.1% (2)
now, - 0.1% (2)
every - 0.1% (2)
pgxn, - 0.1% (2)
search - 0.1% (2)
posts - 0.1% (2)
discussion: - 0.1% (2)
last, - 0.1% (2)
char(x) - 0.1% (2)
github, - 0.1% (2)
varchar - 0.1% (2)
text - 0.1% (2)
extension, - 0.1% (2)
aggregate, - 0.1% (2)
stop - 0.1% (2)
20th, - 0.1% (2)
analyze - 0.1% (2)
irc - 0.1% (2)
help - 0.1% (2)
cab7npqtec-8+zux8_-4zd46v7ypwooefxgndfsq5rg8iblvm1a@mail.gmail.com - 0.1% (2)
now. - 0.1% (2)
unpleasant - 0.1% (2)
latter - 0.1% (2)
consequences. - 0.1% (2)
so, - 0.1% (2)
modifies - 0.1% (2)
pg_upgrade - 0.1% (2)
/proc/1/fd/*” - 0.1% (2)
output - 0.1% (2)
both - 0.1% (2)
layouts; - 0.1% (2)
former - 0.1% (2)
purpose - 0.1% (2)
tool, - 0.1% (2)
while - 0.1% (2)
merely - 0.1% (2)
discussion, - 0.1% (2)
avoids - 0.1% (2)
unnecessary - 0.1% (2)
backward-compatibility - 0.1% (2)
break. - 0.1% (2)
wish - 0.1% (2)
consider - 0.1% (2)
renaming - 0.1% (2)
programs, - 0.1% (2)
switches, - 0.1% (2)
"wal". - 0.1% (2)
however, - 0.1% (2)
that's - 0.1% (2)
protocol - 0.1% (2)
petr - 0.1% (2)
plugin - 0.1% (2)
cross - 0.1% (2)
needed. - 0.1% (2)
short, - 0.1% (2)
generate - 0.1% (2)
isn't - 0.1% (2)
yet - 0.1% (2)
supported - 0.1% (2)
karlsson - 0.1% (2)
andreas - 0.1% (2)
tables, - 0.1% (2)
doesn't - 0.1% (2)
handle - 0.1% (2)
updates - 0.1% (2)
boundaries. - 0.1% (2)
tuple-routing - 0.1% (2)
currently, - 0.1% (2)
ignored. - 0.1% (2)
range-partitioned - 0.1% (2)
list-partitioned. - 0.1% (2)
would - 0.1% (2)
limited - 0.1% (2)
single - 0.1% (2)
column, - 0.1% (2)
sequence-related - 0.1% (2)
involve - 0.1% (2)
columns. - 0.1% (2)
"column" - 0.1% (2)
expression. - 0.1% (2)
random, - 0.1% (2)
partition, - 0.1% (2)
rollbacks - 0.1% (2)
existing - 0.1% (2)
constraints, - 0.1% (2)
those - 0.1% (2)
make - 0.1% (2)
sense - 0.1% (2)
relation - 0.1% (2)
empty; - 0.1% (2)
differences. - 0.1% (2)
important - 0.1% (2)
own. - 0.1% (2)
children - 0.1% (2)
infrastructure, - 0.1% (2)
contain - 0.1% (2)
actual - 0.1% (2)
correct - 0.1% (2)
reuses - 0.1% (2)
7th - 0.1% (2)
has - 0.1% (2)
constraint. - 0.1% (2)
allowed, - 0.1% (2)
mixed. - 0.1% (2)
nulls - 0.1% (2)
unless - 0.1% (2)
does. - 0.1% (2)
tuples - 0.1% (2)
inserted - 0.1% (2)
automatically - 0.1% (2)
routed - 0.1% (2)
because - 0.1% (2)
general - 0.1% (2)
workers - 0.1% (2)
rijkers, - 0.1% (2)
tested - 0.1% (2)
haas, - 0.1% (2)
bapat, - 0.1% (2)
kapila, - 0.1% (2)
rajkumar - 0.1% (2)
raghuwanshi, - 0.1% (2)
corey - 0.1% (2)
huinker, - 0.1% (2)
jaime - 0.1% (2)
casanova, - 0.1% (2)
rushabh - 0.1% (2)
lathia, - 0.1% (2)
among - 0.1% (2)
langote, - 0.1% (2)
others. - 0.1% (2)
minor - 0.1% (2)
revisions - 0.1% (2)
sequence, - 0.1% (2)
downtime - 0.1% (2)
freund - 0.1% (2)
major, - 0.1% (2)
andres - 0.1% (2)
singer - 0.1% (2)
steve - 0.1% (2)
jelinek - 0.1% (2)
non-inherited - 0.1% (2)
from: - 0.1% (2)
december, - 0.1% (2)
move - 0.1% (2)
previously - 0.1% (2)
including - 0.1% (2)
inheritance, - 0.1% (2)
hoped - 0.1% (2)
whereas - 0.1% (2)
easier - 0.1% (2)
commands, - 0.1% (2)
properties - 0.1% (2)
therefore - 0.1% (2)
transactionally - 0.1% (2)
better - 0.1% (2)
foundation - 0.1% (2)
variety - 0.1% (2)
operated - 0.1% (2)
optimizations, - 0.1% (2)
query - 0.1% (2)
possible. - 0.1% (2)
separates - 0.1% (2)
optimizations. - 0.1% (2)
object. - 0.1% (2)
heap - 0.1% (2)
storing - 0.1% (2)
example - 0.1% (2)
this, - 0.1% (2)
seems - 0.1% (2)
likely - 0.1% (2)
etc.) - 0.1% (2)
useful - 0.1% (2)
increment, - 0.1% (2)
(start, - 0.1% (2)
blog - 0.1% (2)
of the - 0.58% (11)
depesz | - 0.52% (10)
by depesz - 0.52% (10)
| tags: - 0.52% (10)
views | - 0.52% (10)
more » - 0.47% (9)
logical replication - 0.47% (9)
read more - 0.47% (9)
0 comments - 0.42% (8)
waiting for - 0.42% (8)
to the - 0.42% (8)
comments » - 0.37% (7)
table partitioning - 0.37% (7)
the parent - 0.31% (6)
ashutosh bapat - 0.31% (6)
10 – - 0.31% (6)
postgresql 10 - 0.31% (6)
for postgresql - 0.31% (6)
partitioning is - 0.31% (6)
2017 by - 0.31% (6)
write a - 0.26% (5)
» waiting - 0.26% (5)
system catalog - 0.26% (5)
instead of - 0.26% (5)
robert haas - 0.26% (5)
is not - 0.26% (5)
committed patch: - 0.26% (5)
aggregates to - 0.26% (5)
directory to - 0.26% (5)
can be - 0.21% (4)
sequence metadata - 0.21% (4)
and it - 0.21% (4)
tuple routing - 0.21% (4)
ddl commands - 0.21% (4)
the old - 0.21% (4)
to "pg_wal". - 0.21% (4)
now that - 0.21% (4)
"pg_xlog" directory - 0.21% (4)
erik rijkers - 0.21% (4)
by me. - 0.21% (4)
into the - 0.21% (4)
1 comment - 0.21% (4)
the sequence - 0.21% (4)
2016 by - 0.21% (4)
this patch - 0.21% (4)
may not - 0.21% (4)
and ddl - 0.21% (4)
peter eisentraut - 0.21% (4)
are not - 0.21% (4)
the upper - 0.21% (4)
all of - 0.21% (4)
to remote - 0.16% (3)
haas committed - 0.16% (3)
postgres_fdw: push - 0.16% (3)
pg_sequence system - 0.16% (3)
6th, 2017 - 0.16% (3)
20th of - 0.16% (3)
will be - 0.16% (3)
down aggregates - 0.16% (3)
push down - 0.16% (3)
in the - 0.16% (3)
getting first - 0.16% (3)
remote servers. - 0.16% (3)
for some - 0.16% (3)
february 6th, - 0.16% (3)
implement table - 0.16% (3)
and last - 0.16% (3)
pg10, postgresql, - 0.16% (3)
on 20th - 0.16% (3)
and aggregating - 0.1% (2)
the rows - 0.1% (2)
of fetching - 0.1% (2)
side instead - 0.1% (2)
the remote - 0.1% (2)
to push - 0.1% (2)
planner uses - 0.1% (2)
to arrange - 0.1% (2)
paths, and - 0.1% (2)
for foreign - 0.1% (2)
it's possible - 0.1% (2)
planning process, - 0.1% (2)
paths into - 0.1% (2)
to inject - 0.1% (2)
proper hooks - 0.1% (2)
we have - 0.1% (2)
data wrappers - 0.1% (2)
there is - 0.1% (2)
october, robert - 0.1% (2)
are also - 0.1% (2)
planner optimizations. - 0.1% (2)
the tuple - 0.1% (2)
routing based - 0.1% (2)
which this - 0.1% (2)
patch does - 0.1% (2)
based on - 0.1% (2)
the implicit - 0.1% (2)
partitioning constraints - 0.1% (2)
example of - 0.1% (2)
this, but - 0.1% (2)
it seems - 0.1% (2)
likely that - 0.1% (2)
many other - 0.1% (2)
useful optimizations - 0.1% (2)
possible. amit - 0.1% (2)
25th, 2016 - 0.1% (2)
casanova, rushabh - 0.1% (2)
this figures - 0.1% (2)
me. read - 0.1% (2)
revisions by - 0.1% (2)
others. minor - 0.1% (2)
rijkers, among - 0.1% (2)
lathia, erik - 0.1% (2)
huinker, jaime - 0.1% (2)
langote, reviewed - 0.1% (2)
raghuwanshi, corey - 0.1% (2)
kapila, rajkumar - 0.1% (2)
bapat, amit - 0.1% (2)
haas, ashutosh - 0.1% (2)
by robert - 0.1% (2)
and tested - 0.1% (2)
them locally. - 0.1% (2)
abbreviation for - 0.1% (2)
a massive - 0.1% (2)
that's still - 0.1% (2)
merely avoids - 0.1% (2)
an unnecessary - 0.1% (2)
backward-compatibility break. - 0.1% (2)
we may - 0.1% (2)
wish to - 0.1% (2)
consider renaming - 0.1% (2)
other programs, - 0.1% (2)
switches, and - 0.1% (2)
functions which - 0.1% (2)
still use - 0.1% (2)
"xlog" naming - 0.1% (2)
to also - 0.1% (2)
refer to - 0.1% (2)
"wal". however, - 0.1% (2)
under discussion, - 0.1% (2)
tool, while - 0.1% (2)
last values - 0.1% (2)
“sudo ls - 0.1% (2)
why does - 0.1% (2)
comments waiting - 0.1% (2)
comments why - 0.1% (2)
vs. varchar - 0.1% (2)
per group - 0.1% (2)
first and - 0.1% (2)
so let's - 0.1% (2)
i'll write - 0.1% (2)
michael paquier - 0.1% (2)
discussion: cab7npqtec-8+zux8_-4zd46v7ypwooefxgndfsq5rg8iblvm1a@mail.gmail.com - 0.1% (2)
for now. - 0.1% (2)
this much - 0.1% (2)
do just - 0.1% (2)
the latter - 0.1% (2)
the purpose - 0.1% (2)
win for - 0.1% (2)
testing by - 0.1% (2)
possible optimizations, - 0.1% (2)
particularly clear - 0.1% (2)
"xlog" is - 0.1% (2)
cosmetic changes - 0.1% (2)
various mostly - 0.1% (2)
prabhat sahu. - 0.1% (2)
with additional - 0.1% (2)
sometimes confuses - 0.1% (2)
reviewed by - 0.1% (2)
ashutosh bapat. - 0.1% (2)
chalke and - 0.1% (2)
it. jeevan - 0.1% (2)
teach postgres_fdw - 0.1% (2)
performance, so - 0.1% (2)
"write-ahead log", - 0.1% (2)
users into - 0.1% (2)
necessary given - 0.1% (2)
and pg_basebackup - 0.1% (2)
former is - 0.1% (2)
layouts; the - 0.1% (2)
new directory - 0.1% (2)
old and - 0.1% (2)
both the - 0.1% (2)
to understand - 0.1% (2)
modifies pg_upgrade - 0.1% (2)
believe that - 0.1% (2)
the directory - 0.1% (2)
so, rename - 0.1% (2)
unpleasant consequences. - 0.1% (2)
leading to - 0.1% (2)
critical data, - 0.1% (2)
the contents - 0.1% (2)
including query - 0.1% (2)
limited to - 0.1% (2)
variety of - 0.1% (2)
a proper - 0.1% (2)
data. sequence - 0.1% (2)
metadata from - 0.1% (2)
separates the - 0.1% (2)
object. this - 0.1% (2)
sequence heap - 0.1% (2)
storing it - 0.1% (2)
etc.) into - 0.1% (2)
now operated - 0.1% (2)
(start, increment, - 0.1% (2)
catalog move - 0.1% (2)
eisentraut committed - 0.1% (2)
– add - 0.1% (2)
reviewed-by: peter - 0.1% (2)
freund reviewed-by: - 0.1% (2)
metadata is - 0.1% (2)
on transactionally - 0.1% (2)
steve singer - 0.1% (2)
of december, - 0.1% (2)
but there - 0.1% (2)
existing infrastructure, - 0.1% (2)
reuses much - 0.1% (2)
inheritance and - 0.1% (2)
like table - 0.1% (2)
partitioning. table - 0.1% (2)
to some - 0.1% (2)
by ddl - 0.1% (2)
i figured - 0.1% (2)
andreas karlsson - 0.1% (2)
ignored. reviewed-by: - 0.1% (2)
would be - 0.1% (2)
of sequence-related - 0.1% (2)
previously rollbacks - 0.1% (2)
commands, whereas - 0.1% (2)
reviewed-by: andres - 0.1% (2)
jelinek reviewed-by: - 0.1% (2)
important differences. - 0.1% (2)
february 20th, - 0.1% (2)
protocol and - 0.1% (2)
- define - 0.1% (2)
subscription catalog - 0.1% (2)
publication catalogs - 0.1% (2)
replication, upgrade - 0.1% (2)
tags: logical, - 0.1% (2)
/proc/1/fd/*” fail? - 0.1% (2)
workers from: - 0.1% (2)
does “sudo - 0.1% (2)
you can - 0.1% (2)
couple of - 0.1% (2)
pgxn, postgresql - 0.1% (2)
20th, 2017 - 0.1% (2)
values per - 0.1% (2)
output plugin - 0.1% (2)
petr jelinek - 0.1% (2)
from: petr - 0.1% (2)
catalog and - 0.1% (2)
replication workers - 0.1% (2)
add logical - 0.1% (2)
plugin - - 0.1% (2)
and output - 0.1% (2)
replication protocol - 0.1% (2)
define logical - 0.1% (2)
add subscription - 0.1% (2)
reviewed-by: steve - 0.1% (2)
catalogs and - 0.1% (2)
add publication - 0.1% (2)
replication - - 0.1% (2)
rijkers reviewed-by: - 0.1% (2)
reviewed-by: erik - 0.1% (2)
andres freund - 0.1% (2)
singer reviewed-by: - 0.1% (2)
are some - 0.1% (2)
is called - 0.1% (2)
better foundation - 0.1% (2)
handle updates - 0.1% (2)
a single - 0.1% (2)
list-partitioned. list - 0.1% (2)
range-partitioned or - 0.1% (2)
currently, tables - 0.1% (2)
partition boundaries. - 0.1% (2)
that cross - 0.1% (2)
it doesn't - 0.1% (2)
range partitioning - 0.1% (2)
tables, and - 0.1% (2)
are foreign - 0.1% (2)
partitions which - 0.1% (2)
supported for - 0.1% (2)
isn't yet - 0.1% (2)
not needed. - 0.1% (2)
column, but - 0.1% (2)
can involve - 0.1% (2)
on insert - 0.1% (2)
be easier - 0.1% (2)
will serve - 0.1% (2)
that this - 0.1% (2)
and therefore - 0.1% (2)
of partitions, - 0.1% (2)
about properties - 0.1% (2)
to reason - 0.1% (2)
it will - 0.1% (2)
multiple columns. - 0.1% (2)
hoped that - 0.1% (2)
table inheritance, - 0.1% (2)
general than - 0.1% (2)
is less - 0.1% (2)
expression. because - 0.1% (2)
"column" can - 0.1% (2)
a partitioning - 0.1% (2)
triggers are - 0.1% (2)
so tuple-routing - 0.1% (2)
a partitioned - 0.1% (2)
relation with - 0.1% (2)
and contain - 0.1% (2)
called partitions - 0.1% (2)
children are - 0.1% (2)
own. the - 0.1% (2)
of its - 0.1% (2)
no data - 0.1% (2)
no sense - 0.1% (2)
data. each - 0.1% (2)
those make - 0.1% (2)
constraints, since - 0.1% (2)
or non-inherited - 0.1% (2)
have indexes - 0.1% (2)
empty; it - 0.1% (2)
is always - 0.1% (2)
table and - 0.1% (2)
the actual - 0.1% (2)
partition has - 0.1% (2)
correct partition, - 0.1% (2)
columns and - 0.1% (2)
automatically routed - 0.1% (2)
parent are - 0.1% (2)
tuples inserted - 0.1% (2)
parent does. - 0.1% (2)
unless the - 0.1% (2)
allow nulls - 0.1% (2)
have extra - 0.1% (2)
an implicit - 0.1% (2)
partitions can't - 0.1% (2)
be mixed. - 0.1% (2)
inheritance can't - 0.1% (2)
partitioning and - 0.1% (2)
allowed, and - 0.1% (2)
multiple inheritance - 0.1% (2)
partitioning constraint. - 0.1% (2)
-l /proc/1/fd/*” - 0.1% (2)
by depesz | - 0.52% (10)
depesz | tags: - 0.52% (10)
read more » - 0.47% (9)
| 0 comments - 0.42% (8)
views | 0 - 0.42% (8)
2017 by depesz - 0.31% (6)
postgresql 10 – - 0.31% (6)
for postgresql 10 - 0.31% (6)
more » waiting - 0.26% (5)
» waiting for - 0.26% (5)
2016 by depesz - 0.21% (4)
table partitioning is - 0.21% (4)
and ddl - - 0.21% (4)
directory to "pg_wal". - 0.21% (4)
all of the - 0.21% (4)
1 comment » - 0.16% (3)
haas committed patch: - 0.16% (3)
implement table partitioning. - 0.16% (3)
robert haas committed - 0.16% (3)
on 20th of - 0.16% (3)
pg_sequence system catalog - 0.16% (3)
down aggregates to - 0.16% (3)
6th, 2017 by - 0.16% (3)
comments » on - 0.16% (3)
postgres_fdw: push down - 0.16% (3)
aggregates to remote - 0.16% (3)
» on 20th - 0.16% (3)
do it. jeevan - 0.1% (2)
mostly cosmetic changes - 0.1% (2)
bapat. reviewed by - 0.1% (2)
ashutosh bapat with - 0.1% (2)
additional testing by - 0.1% (2)
to unpleasant consequences. - 0.1% (2)
prabhat sahu. various - 0.1% (2)
critical data, leading - 0.1% (2)
directory are not - 0.1% (2)
of the "pg_xlog" - 0.1% (2)
that the contents - 0.1% (2)
by me. read - 0.1% (2)
october 25th, 2016 - 0.1% (2)
clear abbreviation for - 0.1% (2)
users into believe - 0.1% (2)
october, robert haas - 0.1% (2)
it sometimes confuses - 0.1% (2)
"write-ahead log", and - 0.1% (2)
"pg_xlog" directory to - 0.1% (2)
"pg_wal". "xlog" is - 0.1% (2)
not a particularly - 0.1% (2)
chalke and ashutosh - 0.1% (2)
and last values - 0.1% (2)
teach postgres_fdw to - 0.1% (2)
and now that - 0.1% (2)
robert haas, ashutosh - 0.1% (2)
bapat, amit kapila, - 0.1% (2)
rajkumar raghuwanshi, corey - 0.1% (2)
huinker, jaime casanova, - 0.1% (2)
rushabh lathia, erik - 0.1% (2)
rijkers, among others. - 0.1% (2)
minor revisions by - 0.1% (2)
me. read more - 0.1% (2)
| tags: aggregate, - 0.1% (2)
remote servers. now - 0.1% (2)
that the upper - 0.1% (2)
planner uses paths, - 0.1% (2)
we have proper - 0.1% (2)
for performance, so - 0.1% (2)
hooks to inject - 0.1% (2)
paths into the - 0.1% (2)
upper planning process, - 0.1% (2)
it's possible for - 0.1% (2)
foreign data wrappers - 0.1% (2)
to arrange to - 0.1% (2)
push aggregates to - 0.1% (2)
the remote side - 0.1% (2)
instead of fetching - 0.1% (2)
rows and aggregating - 0.1% (2)
them locally. this - 0.1% (2)
figures to be - 0.1% (2)
a massive win - 0.1% (2)
so, rename the - 0.1% (2)
tool, while the - 0.1% (2)
this patch modifies - 0.1% (2)
unnecessary backward-compatibility break. - 0.1% (2)
unpleasant consequences. so, - 0.1% (2)
rename the directory - 0.1% (2)
to "pg_wal". this - 0.1% (2)
patch modifies pg_upgrade - 0.1% (2)
and pg_basebackup to - 0.1% (2)
understand both the - 0.1% (2)
old and new - 0.1% (2)
directory layouts; the - 0.1% (2)
former is necessary - 0.1% (2)
given the purpose - 0.1% (2)
of the tool, - 0.1% (2)
while the latter - 0.1% (2)
merely avoids an - 0.1% (2)
we may wish - 0.1% (2)
are not critical - 0.1% (2)
to consider renaming - 0.1% (2)
other programs, switches, - 0.1% (2)
and functions which - 0.1% (2)
still use the - 0.1% (2)
old "xlog" naming - 0.1% (2)
to also refer - 0.1% (2)
to "wal". however, - 0.1% (2)
that's still under - 0.1% (2)
discussion, so let's - 0.1% (2)
do just this - 0.1% (2)
much for now. - 0.1% (2)
discussion: cab7npqtec-8+zux8_-4zd46v7ypwooefxgndfsq5rg8iblvm1a@mail.gmail.com michael - 0.1% (2)
“sudo ls -l - 0.1% (2)
data, leading to - 0.1% (2)
the "pg_xlog" directory - 0.1% (2)
pg_upgrade and pg_basebackup - 0.1% (2)
which still use - 0.1% (2)
to understand both - 0.1% (2)
the old and - 0.1% (2)
new directory layouts; - 0.1% (2)
the former is - 0.1% (2)
necessary given the - 0.1% (2)
purpose of the - 0.1% (2)
amit langote, reviewed - 0.1% (2)
latter merely avoids - 0.1% (2)
an unnecessary backward-compatibility - 0.1% (2)
break. we may - 0.1% (2)
wish to consider - 0.1% (2)
renaming other programs, - 0.1% (2)
switches, and functions - 0.1% (2)
the old "xlog" - 0.1% (2)
the contents of - 0.1% (2)
naming to also - 0.1% (2)
refer to "wal". - 0.1% (2)
however, that's still - 0.1% (2)
under discussion, so - 0.1% (2)
let's do just - 0.1% (2)
this much for - 0.1% (2)
now. discussion: cab7npqtec-8+zux8_-4zd46v7ypwooefxgndfsq5rg8iblvm1a@mail.gmail.com - 0.1% (2)
"xlog" is not - 0.1% (2)
a particularly clear - 0.1% (2)
abbreviation for "write-ahead - 0.1% (2)
log", and it - 0.1% (2)
sometimes confuses users - 0.1% (2)
into believe that - 0.1% (2)
and tested by - 0.1% (2)
which this patch - 0.1% (2)
are also possible. - 0.1% (2)
sequence-related ddl commands - 0.1% (2)
(start, increment, etc.) - 0.1% (2)
into a proper - 0.1% (2)
system catalog instead - 0.1% (2)
of storing it - 0.1% (2)
in the sequence - 0.1% (2)
heap object. this - 0.1% (2)
separates the metadata - 0.1% (2)
from the sequence - 0.1% (2)
data. sequence metadata - 0.1% (2)
is now operated - 0.1% (2)
on transactionally by - 0.1% (2)
ddl commands, whereas - 0.1% (2)
previously rollbacks of - 0.1% (2)
would be ignored. - 0.1% (2)
erik rijkers reviewed-by: - 0.1% (2)
reviewed-by: andreas karlsson - 0.1% (2)
6 comments » - 0.1% (2)
like table inheritance - 0.1% (2)
and reuses much - 0.1% (2)
of the existing - 0.1% (2)
infrastructure, but there - 0.1% (2)
are some important - 0.1% (2)
differences. the parent - 0.1% (2)
is called a - 0.1% (2)
partitioned table and - 0.1% (2)
is always empty; - 0.1% (2)
it may not - 0.1% (2)
have indexes or - 0.1% (2)
move sequence metadata - 0.1% (2)
andres freund reviewed-by: - 0.1% (2)
those make no - 0.1% (2)
plugin - add - 0.1% (2)
does “sudo ls - 0.1% (2)
-l /proc/1/fd/*” fail? - 0.1% (2)
february 20th, 2017 - 0.1% (2)
i'll write a - 0.1% (2)
– logical replication - 0.1% (2)
postgresql, replication, upgrade - 0.1% (2)
| 6 comments - 0.1% (2)
eisentraut committed patch: - 0.1% (2)
logical replication - - 0.1% (2)
add publication catalogs - 0.1% (2)
add subscription catalog - 0.1% (2)
define logical replication - 0.1% (2)
protocol and output - 0.1% (2)
logical replication workers - 0.1% (2)
steve singer reviewed-by: - 0.1% (2)
from: petr jelinek - 0.1% (2)
reviewed-by: steve singer - 0.1% (2)
reviewed-by: andres freund - 0.1% (2)
reviewed-by: erik rijkers - 0.1% (2)
replication - add - 0.1% (2)
publication catalogs and - 0.1% (2)
ddl - add - 0.1% (2)
subscription catalog and - 0.1% (2)
ddl - define - 0.1% (2)
logical replication protocol - 0.1% (2)
and output plugin - 0.1% (2)
- add logical - 0.1% (2)
replication workers from: - 0.1% (2)
petr jelinek reviewed-by: - 0.1% (2)
non-inherited constraints, since - 0.1% (2)
sense for a - 0.1% (2)
other useful optimizations - 0.1% (2)
properties of partitions, - 0.1% (2)
limited to a - 0.1% (2)
single column, but - 0.1% (2)
range partitioning can - 0.1% (2)
involve multiple columns. - 0.1% (2)
a partitioning "column" - 0.1% (2)
can be an - 0.1% (2)
expression. because table - 0.1% (2)
partitioning is less - 0.1% (2)
general than table - 0.1% (2)
inheritance, it is - 0.1% (2)
hoped that it - 0.1% (2)
will be easier - 0.1% (2)
to reason about - 0.1% (2)
and therefore that - 0.1% (2)
range-partitioned or list-partitioned. - 0.1% (2)
this will serve - 0.1% (2)
as a better - 0.1% (2)
foundation for a - 0.1% (2)
variety of possible - 0.1% (2)
optimizations, including query - 0.1% (2)
planner optimizations. the - 0.1% (2)
tuple routing based - 0.1% (2)
20th, 2017 by - 0.1% (2)
does based on - 0.1% (2)
the implicit partitioning - 0.1% (2)
constraints is an - 0.1% (2)
example of this, - 0.1% (2)
but it seems - 0.1% (2)
likely that many - 0.1% (2)
list partitioning is - 0.1% (2)
tables can be - 0.1% (2)
relation with no - 0.1% (2)
columns and may - 0.1% (2)
data of its - 0.1% (2)
own. the children - 0.1% (2)
are called partitions - 0.1% (2)
and contain all - 0.1% (2)
of the actual - 0.1% (2)
data. each partition - 0.1% (2)
has an implicit - 0.1% (2)
partitioning constraint. multiple - 0.1% (2)
inheritance is not - 0.1% (2)
allowed, and partitioning - 0.1% (2)
and inheritance can't - 0.1% (2)
be mixed. partitions - 0.1% (2)
can't have extra - 0.1% (2)
not allow nulls - 0.1% (2)
partition boundaries. currently, - 0.1% (2)
unless the parent - 0.1% (2)
does. tuples inserted - 0.1% (2)
into the parent - 0.1% (2)
are automatically routed - 0.1% (2)
to the correct - 0.1% (2)
partition, so tuple-routing - 0.1% (2)
on insert triggers - 0.1% (2)
are not needed. - 0.1% (2)
tuple routing isn't - 0.1% (2)
yet supported for - 0.1% (2)
partitions which are - 0.1% (2)
foreign tables, and - 0.1% (2)
it doesn't handle - 0.1% (2)
updates that cross - 0.1% (2)
comments waiting for - 0.1% (2)

Here you can find chart of all your popular one, two and three word phrases. Google and others search engines means your page is about words you use frequently.

Copyright © 2015-2016 hupso.pl. All rights reserved. FB | +G | Twitter

Hupso.pl jest serwisem internetowym, w którym jednym kliknieciem możesz szybko i łatwo sprawdź stronę www pod kątem SEO. Oferujemy darmowe pozycjonowanie stron internetowych oraz wycena domen i stron internetowych. Prowadzimy ranking polskich stron internetowych oraz ranking stron alexa.