4.92 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 3689
Text/HTML 49.22 %
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 134
Linki wewnętrzne 2
Linki zewnętrzne 132
Linki bez atrybutu Title 113
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
projects https://www.depesz.com/projects/
contact https://www.depesz.com/contact/
new change on explain.depesz.com https://www.depesz.com/2017/05/19/new-change-on-explain-depesz-com/
explain https://www.depesz.com/tag/explain/
explain.depesz.com https://www.depesz.com/tag/explaindepeszcom/
optimization https://www.depesz.com/tag/optimization/
postgresql https://www.depesz.com/tag/postgresql/
no comments » https://www.depesz.com/2017/05/19/new-change-on-explain-depesz-com/#respond
some plan page https://explain.depesz.com/s/krt2
this one https://explain.depesz.com/s/sepv
read more » https://www.depesz.com/2017/05/19/new-change-on-explain-depesz-com/#more-3261
waiting for postgresql 10 – implement multivariate n-distinct coefficients https://www.depesz.com/2017/05/19/waiting-for-postgresql-10-implement-multivariate-n-distinct-coefficients/
explain https://www.depesz.com/tag/explain/
performance https://www.depesz.com/tag/performance/
pg10 https://www.depesz.com/tag/pg10/
postgresql https://www.depesz.com/tag/postgresql/
statistics https://www.depesz.com/tag/statistics/
1 comment » https://www.depesz.com/2017/05/19/waiting-for-postgresql-10-implement-multivariate-n-distinct-coefficients/#comments
committed http://git.postgresql.org/pg/commitdiff/7b504eb282ca2f5104b5c00b4f05a3ef6bb1385b
committed http://git.postgresql.org/pg/commitdiff/2686ee1b7ccfb9214064d4d2a98ea77382880306
committed http://git.postgresql.org/pg/commitdiff/8c5cdb7f4f6e1d6a6104cb58ce4f23453891651b
committed http://git.postgresql.org/pg/commitdiff/bc085205c8a425fcaa54e27c6dcd83101130439b
read more » https://www.depesz.com/2017/05/19/waiting-for-postgresql-10-implement-multivariate-n-distinct-coefficients/#more-3259
waiting for postgresql 10 – support scram-sha-256 authentication (rfc 5802 and 7677). https://www.depesz.com/2017/04/18/waiting-for-postgresql-10-support-scram-sha-256-authentication-rfc-5802-and-7677/
authentication https://www.depesz.com/tag/authentication/
guc https://www.depesz.com/tag/guc/
password https://www.depesz.com/tag/password/
password_encryption https://www.depesz.com/tag/password_encryption/
pg10 https://www.depesz.com/tag/pg10/
pg_hba https://www.depesz.com/tag/pg_hba/
postgresql https://www.depesz.com/tag/postgresql/
5 comments » https://www.depesz.com/2017/04/18/waiting-for-postgresql-10-support-scram-sha-256-authentication-rfc-5802-and-7677/#comments
committed http://git.postgresql.org/pg/commitdiff/818fd4a67d610991757b610755e3065fb99d80a5
read more » https://www.depesz.com/2017/04/18/waiting-for-postgresql-10-support-scram-sha-256-authentication-rfc-5802-and-7677/#more-3252
waiting for postgresql 10 – identity columns https://www.depesz.com/2017/04/10/waiting-for-postgresql-10-identity-columns/
generated https://www.depesz.com/tag/generated/
identity https://www.depesz.com/tag/identity/
pg10 https://www.depesz.com/tag/pg10/
postgresql https://www.depesz.com/tag/postgresql/
sequence https://www.depesz.com/tag/sequence/
serial https://www.depesz.com/tag/serial/
6 comments » https://www.depesz.com/2017/04/10/waiting-for-postgresql-10-identity-columns/#comments
committed http://git.postgresql.org/pg/commitdiff/3217327053638085d24dd4d276e7c1f7ac2c4c6b
read more » https://www.depesz.com/2017/04/10/waiting-for-postgresql-10-identity-columns/#more-3249
waiting for postgresql 10 – full text search support for json and jsonb https://www.depesz.com/2017/04/04/waiting-for-postgresql-10-full-text-search-support-for-json-and-jsonb/
json https://www.depesz.com/tag/json/
jsonb https://www.depesz.com/tag/jsonb/
pg10 https://www.depesz.com/tag/pg10/
postgresql https://www.depesz.com/tag/postgresql/
to_tsvector https://www.depesz.com/tag/to_tsvector/
tsearch https://www.depesz.com/tag/tsearch/
tsquery https://www.depesz.com/tag/tsquery/
tsvector https://www.depesz.com/tag/tsvector/
3 comments » https://www.depesz.com/2017/04/04/waiting-for-postgresql-10-full-text-search-support-for-json-and-jsonb/#comments
committed http://git.postgresql.org/pg/commitdiff/e306df7f9cd6b4433273e006df11bdc966b7079e
read more » https://www.depesz.com/2017/04/04/waiting-for-postgresql-10-full-text-search-support-for-json-and-jsonb/#more-3247
waiting for postgresql 10 – support \if … \elif … \else … \endif in psql scripting. https://www.depesz.com/2017/04/03/waiting-for-postgresql-10-support-if-elif-else-endif-in-psql-scripting/
conditional https://www.depesz.com/tag/conditional/
else https://www.depesz.com/tag/else/
if https://www.depesz.com/tag/if/
pg10 https://www.depesz.com/tag/pg10/
postgresql https://www.depesz.com/tag/postgresql/
psql https://www.depesz.com/tag/psql/
scripting https://www.depesz.com/tag/scripting/
4 comments » https://www.depesz.com/2017/04/03/waiting-for-postgresql-10-support-if-elif-else-endif-in-psql-scripting/#comments
committed http://git.postgresql.org/pg/commitdiff/e984ef5861df4bc9733b36271d05763e82de7c04
read more » https://www.depesz.com/2017/04/03/waiting-for-postgresql-10-support-if-elif-else-endif-in-psql-scripting/#more-3244
waiting for postgresql 10 – logical replication support for initial data copy https://www.depesz.com/2017/04/03/waiting-for-postgresql-10-logical-replication-support-for-initial-data-copy/
copy https://www.depesz.com/tag/copy/
data https://www.depesz.com/tag/data/
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/
sync https://www.depesz.com/tag/sync/
3 comments » https://www.depesz.com/2017/04/03/waiting-for-postgresql-10-logical-replication-support-for-initial-data-copy/#comments
committed http://git.postgresql.org/pg/commitdiff/7c4f52409a8c7d85ed169bbbc1f6092274d03920
read more » https://www.depesz.com/2017/04/03/waiting-for-postgresql-10-logical-replication-support-for-initial-data-copy/#more-3239
waiting for postgresql 10 – hash indexing vs. wal https://www.depesz.com/2017/03/15/waiting-for-postgresql-10-hash-indexing-vs-wal/
crash https://www.depesz.com/tag/crash/
hash https://www.depesz.com/tag/hash/
pg10 https://www.depesz.com/tag/pg10/
postgresql https://www.depesz.com/tag/postgresql/
recovery https://www.depesz.com/tag/recovery/
replication https://www.depesz.com/tag/replication/
safe https://www.depesz.com/tag/safe/
wal https://www.depesz.com/tag/wal/
1 comment » https://www.depesz.com/2017/03/15/waiting-for-postgresql-10-hash-indexing-vs-wal/#comments
committed http://git.postgresql.org/pg/commitdiff/c11453ce0aeaa377cbbcc9a3fc418acb94629330
read more » https://www.depesz.com/2017/03/15/waiting-for-postgresql-10-hash-indexing-vs-wal/#more-3237
waiting for postgresql 10 – support xmltable query expression https://www.depesz.com/2017/03/09/waiting-for-postgresql-10-support-xmltable-query-expression/
etl https://www.depesz.com/tag/etl/
import https://www.depesz.com/tag/import/
pg10 https://www.depesz.com/tag/pg10/
postgresql https://www.depesz.com/tag/postgresql/
xml https://www.depesz.com/tag/xml/
xmltable https://www.depesz.com/tag/xmltable/
no comments » https://www.depesz.com/2017/03/09/waiting-for-postgresql-10-support-xmltable-query-expression/#respond
committed http://git.postgresql.org/pg/commitdiff/fcec6caafa2346b6c9d3ad5065e417733bd63cd9
read more » https://www.depesz.com/2017/03/09/waiting-for-postgresql-10-support-xmltable-query-expression/#more-3233
waiting for postgresql 10 – psql: add \gx command https://www.depesz.com/2017/03/07/waiting-for-postgresql-10-psql-add-gx-command/
expanded https://www.depesz.com/tag/expanded/
gx https://www.depesz.com/tag/gx/
pg10 https://www.depesz.com/tag/pg10/
postgresql https://www.depesz.com/tag/postgresql/
psql https://www.depesz.com/tag/psql/
no comments » https://www.depesz.com/2017/03/07/waiting-for-postgresql-10-psql-add-gx-command/#respond
committed http://git.postgresql.org/pg/commitdiff/b2678efd43f17db7dfa04e0ca076ea01275cd9bc
read more » https://www.depesz.com/2017/03/07/waiting-for-postgresql-10-psql-add-gx-command/#more-3231
comments rss http://www.depesz.com/comments/feed/
posts rss http://depesz.com/feed/
new change on explain.depesz.com https://www.depesz.com/2017/05/19/new-change-on-explain-depesz-com/
waiting for postgresql 10 – implement multivariate n-distinct coefficients https://www.depesz.com/2017/05/19/waiting-for-postgresql-10-implement-multivariate-n-distinct-coefficients/
explaining the unexplainable – part 3 https://www.depesz.com/2013/05/09/explaining-the-unexplainable-part-3/
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/
explaining the unexplainable – part 2 https://www.depesz.com/2013/04/27/explaining-the-unexplainable-part-2/
waiting for postgresql 10 – full text search support for json and jsonb https://www.depesz.com/2017/04/04/waiting-for-postgresql-10-full-text-search-support-for-json-and-jsonb/
why is upsert so complicated? https://www.depesz.com/2012/06/10/why-is-upsert-so-complicated/
how much ram is postgresql using? https://www.depesz.com/2012/06/09/how-much-ram-is-postgresql-using/
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/
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 projects contact new change on explain.depesz.com may 19th, 2017 by depesz | tags: explain, explain.depesz.com, optimization, postgresql | no comments » some (long) time ago, someone on irc suggested that i add option to keep track of optimizations of queries. sorry, i forgot your name, and the mails disappeared in some crash. anyway – right now, when you are on some plan page, you can press “add optimization" button, and you will be redirected to index page, but when you will add plan there, it will be understood to be plan from optimization of the query. like this one. you can have any number of optimizations per plan, and when viewing plan that has optimizations, or is an optimization of earlier plan – you will see this above plan table. whether you'll use it – it's up to you. someone wanted it, and it looked like sensible thing to add, so there it is 🙂 read more » waiting for postgresql 10 – implement multivariate n-distinct coefficients may 19th, 2017 by depesz | tags: explain, performance, pg10, postgresql, statistics | 1 comment » i missed it completely, but on 24th of march 2017, alvaro herrera committed patch: implement multivariate n-distinct coefficients add support for explicitly declared statistic objects (create statistics), allowing collection of statistics on more complex combinations that individual table columns. companion commands drop statistics and alter statistics ... owner to / set schema / rename are added too. all this ddl has been designed so that more statistic types can be added later on, such as multivariate most-common-values and multivariate histograms between columns of a single table, leaving room for permitting columns on multiple tables, too, as well as expressions. this commit only adds support for collection of n-distinct coefficient on user-specified sets of columns in a single table. this is useful to estimate number of distinct groups in group by and distinct clauses; estimation errors there can cause over-allocation of memory in hashed aggregates, for instance, so it's a worthwhile problem to solve. a new special pseudo-type pg_ndistinct is used. (num-distinct estimation was deemed sufficiently useful by itself that this is worthwhile even if no further statistic types are added immediately; so much so that another version of essentially the same functionality was submitted by kyotaro horiguchi: https://postgr.es/m/.173334..horiguchi.kyotaro@lab.ntt.co.jp though this commit does not use that code.) author: tomas vondra. some code rework by álvaro. ideriha takeshi discussion: https://postgr.es/m/.4080608@fuzzy.cz https://postgr.es/m/.ixlaueanxegqd5gr@alvherre.pgsqlimplement multivariate n-distinct coefficients add support for explicitly declared statistic objects (create statistics), allowing collection of statistics on more complex combinations that individual table columns. companion commands drop statistics and alter statistics ... owner to / set schema / rename are added too. all this ddl has been designed so that more statistic types can be added later on, such as multivariate most-common-values and multivariate histograms between columns of a single table, leaving room for permitting columns on multiple tables, too, as well as expressions. this commit only adds support for collection of n-distinct coefficient on user-specified sets of columns in a single table. this is useful to estimate number of distinct groups in group by and distinct clauses; estimation errors there can cause over-allocation of memory in hashed aggregates, for instance, so it's a worthwhile problem to solve. a new special pseudo-type pg_ndistinct is used. (num-distinct estimation was deemed sufficiently useful by itself that this is worthwhile even if no further statistic types are added immediately; so much so that another version of essentially the same functionality was submitted by kyotaro horiguchi: https://postgr.es/m/.173334..horiguchi.kyotaro@lab.ntt.co.jp though this commit does not use that code.) author: tomas vondra. some code rework by álvaro. ideriha takeshi discussion: https://postgr.es/m/.4080608@fuzzy.cz https://postgr.es/m/.ixlaueanxegqd5gr@alvherre.pgsql afterwards, there were couple more commits related to it: on 5th of april 2017, patch committed by simon riggs on 17th of april 2017, patch committed by alvaro herrera on 12nd of may 2017, patch committed by alvaro herrera read more » waiting for postgresql 10 – support scram-sha-256 authentication (rfc 5802 and 7677). april 18th, 2017 by depesz | tags: authentication, guc, password, password_encryption, pg10, pg_hba, postgresql | 5 comments » on 7th of march 2017, heikki linnakangas committed patch: support scram-sha-256 authentication (rfc 5802 and 7677). this introduces a new generic sasl authentication method, similar to the gss and sspi methods. the server first tells the client which sasl authentication mechanism to use, and then the mechanism-specific sasl messages are exchanged in authenticationsaslcontinue and passwordmessage messages. only scram-sha-256 is supported at the moment, but this allows adding more sasl mechanisms in the future, without changing the overall protocol. support for channel binding, aka scram-sha-256-plus is left for later. the saslprep algorithm, for pre-processing the password, is not yet implemented. that could cause trouble, if you use a password with non-ascii characters, and a client library that does implement saslprep. that will hopefully be added later. authorization identities, as specified in the scram-sha-256 specification, are ignored. set session authorization provides more or less the same functionality, anyway. if a user doesn't exist, perform a "mock" authentication, by constructing an authentic-looking challenge on the fly. the challenge is derived from a new system-wide random value, "mock authentication nonce", which is created at initdb, and stored in the control file. we go through these motions, in order to not give away the information on whether the user exists, to unauthenticated users. bumps pg_control_version, because of the new field in control file. patch by michael paquier and heikki linnakangas, reviewed at different stages by robert haas, stephen frost, david steele, aleksander alekseev, and many others. discussion: https://www.postgresql.org/message-id/cab7npqrbr3gmfydedcahzukfkrgbltltmvenomprvwreszkf8g%40mail.gmail.com discussion: https://www.postgresql.org/message-id/cab7npqsmxu35g%3dw9x74hveqp0uvgjxvyoua4a-a3m%2b0wfebv-w%40mail.gmail.com discussion: https://www.postgresql.org/message-id/.6080106@iki.fisupport scram-sha-256 authentication (rfc 5802 and 7677). this introduces a new generic sasl authentication method, similar to the gss and sspi methods. the server first tells the client which sasl authentication mechanism to use, and then the mechanism-specific sasl messages are exchanged in authenticationsaslcontinue and passwordmessage messages. only scram-sha-256 is supported at the moment, but this allows adding more sasl mechanisms in the future, without changing the overall protocol. support for channel binding, aka scram-sha-256-plus is left for later. the saslprep algorithm, for pre-processing the password, is not yet implemented. that could cause trouble, if you use a password with non-ascii characters, and a client library that does implement saslprep. that will hopefully be added later. authorization identities, as specified in the scram-sha-256 specification, are ignored. set session authorization provides more or less the same functionality, anyway. if a user doesn't exist, perform a "mock" authentication, by constructing an authentic-looking challenge on the fly. the challenge is derived from a new system-wide random value, "mock authentication nonce", which is created at initdb, and stored in the control file. we go through these motions, in order to not give away the information on whether the user exists, to unauthenticated users. bumps pg_control_version, because of the new field in control file. patch by michael paquier and heikki linnakangas, reviewed at different stages by robert haas, stephen frost, david steele, aleksander alekseev, and many others. discussion: https://www.postgresql.org/message-id/cab7npqrbr3gmfydedcahzukfkrgbltltmvenomprvwreszkf8g%40mail.gmail.com discussion: https://www.postgresql.org/message-id/cab7npqsmxu35g%3dw9x74hveqp0uvgjxvyoua4a-a3m%2b0wfebv-w%40mail.gmail.com discussion: https://www.postgresql.org/message-id/.6080106@iki.fi read more » waiting for postgresql 10 – identity columns april 10th, 2017 by depesz | tags: generated, identity, pg10, postgresql, sequence, serial | 6 comments » on 6th of april 2017, peter eisentraut committed patch: identity columns this is the sql standard-conforming variant of postgresql's serial columns. it fixes a few usability issues that serial columns have: - create table / like copies default but refers to same sequence - cannot add/drop serialness with alter table - dropping default does not drop sequence - need to grant separate privileges to sequence - other slight weirdnesses because serial is some kind of special macroidentity columns this is the sql standard-conforming variant of postgresql's serial columns. it fixes a few usability issues that serial columns have: - create table / like copies default but refers to same sequence - cannot add/drop serialness with alter table - dropping default does not drop sequence - need to grant separate privileges to sequence - other slight weirdnesses because serial is some kind of special macro read more » waiting for postgresql 10 – full text search support for json and jsonb april 4th, 2017 by depesz | tags: json, jsonb, pg10, postgresql, to_tsvector, tsearch, tsquery, tsvector | 3 comments » on 31st of march 2017, andrew dunstan committed patch: full text search support for json and jsonb the new functions are ts_headline() and to_tsvector. dmitry dolgov, edited and documented by me.full text search support for json and jsonb the new functions are ts_headline() and to_tsvector. dmitry dolgov, edited and documented by me. read more » waiting for postgresql 10 – support \if … \elif … \else … \endif in psql scripting. april 3rd, 2017 by depesz | tags: conditional, else, if, pg10, postgresql, psql, scripting | 4 comments » on 30th of march 2017, tom lane committed patch: support \if ... \elif ... \else ... \endif in psql scripting. this patch adds nestable conditional blocks to psql. the control structure feature per se is complete, but the boolean expressions understood by \if and \elif are pretty primitive; basically, after variable substitution and backtick expansion, the result has to be "true" or "false" or one of the other standard spellings of a boolean value. but that's enough for many purposes, since you can always do the heavy lifting on the server side; and we can extend it later. along the way, pay down some of the technical debt that had built up around psql/command.c: * refactor exec_command() into a function per command, instead of being a 1500-line monstrosity. this makes the file noticeably longer because of repetitive function header/trailer overhead, but it seems much more readable. * teach psql_get_variable() and psqlscanslash.l to suppress variable substitution and backtick expansion on the basis of the conditional stack state, thereby allowing removal of the ot_no_eval kluge. * fix the no-doubt-once-expedient hack of sometimes silently substituting mainloop.c's previous_buf for query_buf when calling handleslashcmds. (it's a bit remarkable that commands like \r worked at all with that.) recall of a previous query is now done explicitly in the slash commands where that should happen. corey huinker, reviewed by fabien coelho, further hacking by me discussion: https://postgr.es/m/cadklm=c94osrtnat=lx0ivnq4pxdneoomffyvbkm5n_xfmltaa@mail.gmail.comsupport \if ... \elif ... \else ... \endif in psql scripting. this patch adds nestable conditional blocks to psql. the control structure feature per se is complete, but the boolean expressions understood by \if and \elif are pretty primitive; basically, after variable substitution and backtick expansion, the result has to be "true" or "false" or one of the other standard spellings of a boolean value. but that's enough for many purposes, since you can always do the heavy lifting on the server side; and we can extend it later. along the way, pay down some of the technical debt that had built up around psql/command.c: * refactor exec_command() into a function per command, instead of being a 1500-line monstrosity. this makes the file noticeably longer because of repetitive function header/trailer overhead, but it seems much more readable. * teach psql_get_variable() and psqlscanslash.l to suppress variable substitution and backtick expansion on the basis of the conditional stack state, thereby allowing removal of the ot_no_eval kluge. * fix the no-doubt-once-expedient hack of sometimes silently substituting mainloop.c's previous_buf for query_buf when calling handleslashcmds. (it's a bit remarkable that commands like \r worked at all with that.) recall of a previous query is now done explicitly in the slash commands where that should happen. corey huinker, reviewed by fabien coelho, further hacking by me discussion: https://postgr.es/m/cadklm=c94osrtnat=lx0ivnq4pxdneoomffyvbkm5n_xfmltaa@mail.gmail.com read more » waiting for postgresql 10 – logical replication support for initial data copy april 3rd, 2017 by depesz | tags: copy, data, logical, pg10, postgresql, replication, sync | 3 comments » on 23rd of march 2017, peter eisentraut committed patch: logical replication support for initial data copy add functionality for a new subscription to copy the initial data in the tables and then sync with the ongoing apply process. for the copying, add a new internal copy option to have the copy source data provided by a callback function. the initial data copy works on the subscriber by receiving copy data from the publisher and then providing it locally into a copy that writes to the destination table. a wal receiver can now execute full sql commands. this is used here to obtain information about tables and publications. several new options were added to create and alter subscription to control whether and when initial table syncing happens. change pg_dump option --no-create-subscription-slots to --no-subscription-connect and use the new create subscription ... noconnect option for that. author: petr jelineklogical replication support for initial data copy add functionality for a new subscription to copy the initial data in the tables and then sync with the ongoing apply process. for the copying, add a new internal copy option to have the copy source data provided by a callback function. the initial data copy works on the subscriber by receiving copy data from the publisher and then providing it locally into a copy that writes to the destination table. a wal receiver can now execute full sql commands. this is used here to obtain information about tables and publications. several new options were added to create and alter subscription to control whether and when initial table syncing happens. change pg_dump option --no-create-subscription-slots to --no-subscription-connect and use the new create subscription ... noconnect option for that. author: petr jelinek read more » waiting for postgresql 10 – hash indexing vs. wal march 15th, 2017 by depesz | tags: crash, hash, pg10, postgresql, recovery, replication, safe, wal | 1 comment » for a long time hash indexed were not crash safe, and couldn't be used on replication slave, because they skipped wal. now, thanks to these two commits, it has changed: on 14th of march 2017, robert haas committed patch: hash: add write-ahead logging support. the warning about hash indexes not being write-ahead logged and their use being discouraged has been removed. "snapshot too old" is now supported for tables with hash indexes. most importantly, barring bugs, hash indexes will now be crash-safe and usable on standbys. this commit doesn't yet add wal consistency checking for hash indexes, as we now have for other index types; a separate patch has been submitted to cure that lack. amit kapila, reviewed and slightly modified by me. the larger patch series of which this is a part has been reviewed and tested by álvaro herrera, ashutosh sharma, mark kirkwood, jeff janes, and jesper pedersen. discussion: http://postgr.es/m/caa4ek1jobx=yu33631qh-xivyxtpsalh514+jr8xed7v+k3r_q@mail.gmail.comhash: add write-ahead logging support. the warning about hash indexes not being write-ahead logged and their use being discouraged has been removed. "snapshot too old" is now supported for tables with hash indexes. most importantly, barring bugs, hash indexes will now be crash-safe and usable on standbys. this commit doesn't yet add wal consistency checking for hash indexes, as we now have for other index types; a separate patch has been submitted to cure that lack. amit kapila, reviewed and slightly modified by me. the larger patch series of which this is a part has been reviewed and tested by álvaro herrera, ashutosh sharma, mark kirkwood, jeff janes, and jesper pedersen. discussion: http://postgr.es/m/caa4ek1jobx=yu33631qh-xivyxtpsalh514+jr8xed7v+k3r_q@mail.gmail.com and then, ~ 13 hours later, robert committed also: hash: support wal consistency checking. kuntal ghosh, reviewed by amit kapila and ashutosh sharma, with a few tweaks by me. discussion: http://postgr.es/m/cagz5qcjlerun_zoo0edv6_y_d0o4tntmper7ivtlbg4rurjdwg@mail.gmail.comhash: support wal consistency checking. kuntal ghosh, reviewed by amit kapila and ashutosh sharma, with a few tweaks by me. discussion: http://postgr.es/m/cagz5qcjlerun_zoo0edv6_y_d0o4tntmper7ivtlbg4rurjdwg@mail.gmail.com read more » waiting for postgresql 10 – support xmltable query expression march 9th, 2017 by depesz | tags: etl, import, pg10, postgresql, xml, xmltable | no comments » on 8th of march, alvaro herrera committed patch: xmltable is defined by the sql/xml standard as a feature that allows turning xml-formatted data into relational form, so that it can be used as a

in the from clause of a query. this new construct provides significant simplicity and performance benefit for xml data processing; what in a client-side custom implementation was reported to take 20 minutes can be executed in 400ms using xmltable. (the same functionality was said to take 10 seconds using nested postgresql xpath function calls, and 5 seconds using xmlreader under pl/python). the implemented syntax deviates slightly from what the standard requires. first, the standard indicates that the passing clause is optional and that multiple xml input documents may be given to it; we make it mandatory and accept a single document only. second, we don't currently support a default namespace to be specified. this implementation relies on a new executor node based on a hardcoded method table. (because the grammar is fixed, there is no extensibility in the current approach; further constructs can be implemented on top of this such as json_table, but they require changes to core code.) author: pavel stehule, álvaro herrera extensively reviewed by: craig ringer discussion: https://postgr.es/m/cafj8pragfzmd-losmnmgybd0wseznlhwap8do79+-gtrapr4qa@mail.gmail.comxmltable is defined by the sql/xml standard as a feature that allows turning xml-formatted data into relational form, so that it can be used as a
in the from clause of a query. this new construct provides significant simplicity and performance benefit for xml data processing; what in a client-side custom implementation was reported to take 20 minutes can be executed in 400ms using xmltable. (the same functionality was said to take 10 seconds using nested postgresql xpath function calls, and 5 seconds using xmlreader under pl/python). the implemented syntax deviates slightly from what the standard requires. first, the standard indicates that the passing clause is optional and that multiple xml input documents may be given to it; we make it mandatory and accept a single document only. second, we don't currently support a default namespace to be specified. this implementation relies on a new executor node based on a hardcoded method table. (because the grammar is fixed, there is no extensibility in the current approach; further constructs can be implemented on top of this such as json_table, but they require changes to core code.) author: pavel stehule, álvaro herrera extensively reviewed by: craig ringer discussion: https://postgr.es/m/cafj8pragfzmd-losmnmgybd0wseznlhwap8do79+-gtrapr4qa@mail.gmail.com read more » waiting for postgresql 10 – psql: add \gx command march 7th, 2017 by depesz | tags: expanded, gx, pg10, postgresql, psql | no comments » on 7th of march, stephen frost committed patch: psql: add \gx command it can often be useful to use expanded mode output (\x) for just a single query. introduce a \gx which acts exactly like \g except that it will force expanded output mode for that one \gx call. this is simpler than having to use \x as a toggle and also means that the user doesn't have to worry about the current state of the expanded variable, or resetting it later, to ensure a given query is always returned in expanded mode. primairly christoph's patch, though i did tweak the documentation and help text a bit, and re-indented the tab completion section. author: christoph berg reviewed by: daniel verite discussion: https://www.postgresql.org/message-id/20170127132737.6skslelaf4txs6iw%40msg.credativ.depsql: add \gx command it can often be useful to use expanded mode output (\x) for just a single query. introduce a \gx which acts exactly like \g except that it will force expanded output mode for that one \gx call. this is simpler than having to use \x as a toggle and also means that the user doesn't have to worry about the current state of the expanded variable, or resetting it later, to ensure a given query is always returned in expanded mode. primairly christoph's patch, though i did tweak the documentation and help text a bit, and re-indented the tab completion section. author: christoph berg reviewed by: daniel verite discussion: https://www.postgresql.org/message-id/20170127132737.6skslelaf4txs6iw%40msg.credativ.de read more » search follow me comments rss posts rss popular posts new change on explain.depesz.com 578 views | 0 comments waiting for postgresql 10 – implement multivariate n-distinct coefficients 492 views | 1 comment explaining the unexplainable – part 3 215 views | 0 comments char(x) vs. varchar(x) vs. varchar vs. text – updated 2010-03-03 181 views | 0 comments explaining the unexplainable – part 2 176 views | 0 comments waiting for postgresql 10 – full text search support for json and jsonb 160 views | 0 comments why is upsert so complicated? 154 views | 0 comments how much ram is postgresql using? 133 views | 0 comments how i learned to stop worrying and love the triggers 130 views | 0 comments waiting for 9.6 – add if not exists processing to alter table add column 116 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: 3440

One word

Two words phrases

Three words phrases

the - 5.47% (188)
and - 3.87% (133)
for - 2.15% (74)
sql - 1.74% (60)
use - 1.66% (57)
that - 1.45% (50)
tab - 1.16% (40)
table - 1.1% (38)
add - 1.08% (37)
this - 1.05% (36)
postgresql - 1.05% (36)
all - 1.05% (36)
support - 0.87% (30)
has - 0.84% (29)
can - 0.76% (26)
then - 0.73% (25)
new - 0.7% (24)
2017 - 0.7% (24)
patch - 0.64% (22)
commit - 0.61% (21)
more - 0.61% (21)
comment - 0.61% (21)
not - 0.52% (18)
discussion: - 0.52% (18)
copy - 0.52% (18)
function - 0.52% (18)
- 0.52% (18)
comments - 0.52% (18)
xml - 0.49% (17)
command - 0.49% (17)
on, - 0.49% (17)
hash - 0.49% (17)
implement - 0.47% (16)
column - 0.47% (16)
per - 0.47% (16)
data - 0.47% (16)
psql - 0.47% (16)
are - 0.47% (16)
columns - 0.44% (15)
but - 0.44% (15)
statistic - 0.44% (15)
you - 0.44% (15)
sasl - 0.41% (14)
ram - 0.41% (14)
read - 0.41% (14)
with - 0.41% (14)
distinct - 0.41% (14)
authentication - 0.41% (14)
reviewed - 0.41% (14)
committed - 0.38% (13)
query - 0.38% (13)
index - 0.38% (13)
cause - 0.38% (13)
depesz - 0.38% (13)
some - 0.38% (13)
here - 0.38% (13)
now - 0.35% (12)
json - 0.35% (12)
create - 0.35% (12)
does - 0.35% (12)
waiting - 0.35% (12)
option - 0.32% (11)
later - 0.32% (11)
march - 0.32% (11)
explain - 0.29% (10)
other - 0.29% (10)
standard - 0.29% (10)
added - 0.29% (10)
tags: - 0.29% (10)
subscription - 0.29% (10)
will - 0.29% (10)
2017, - 0.29% (10)
views - 0.29% (10)
control - 0.29% (10)
... - 0.29% (10)
user - 0.29% (10)
one - 0.26% (9)
wal - 0.26% (9)
there - 0.26% (9)
document - 0.26% (9)
initial - 0.26% (9)
table. - 0.26% (9)
too - 0.26% (9)
expanded - 0.26% (9)
scram-sha-256 - 0.26% (9)
have - 0.26% (9)
because - 0.26% (9)
patch: - 0.26% (9)
change - 0.26% (9)
serial - 0.26% (9)
statistics - 0.26% (9)
pg10, - 0.26% (9)
from - 0.26% (9)
single - 0.23% (8)
code - 0.23% (8)
april - 0.23% (8)
author: - 0.23% (8)
password - 0.23% (8)
variable - 0.23% (8)
full - 0.23% (8)
was - 0.23% (8)
same - 0.23% (8)
functionality - 0.23% (8)
which - 0.23% (8)
commands - 0.23% (8)
set - 0.23% (8)
any - 0.23% (8)
multivariate - 0.23% (8)
drop - 0.23% (8)
herrera - 0.23% (8)
postgresql, - 0.23% (8)
indexes - 0.23% (8)
like - 0.23% (8)
been - 0.23% (8)
press - 0.23% (8)
plan - 0.23% (8)
tables - 0.23% (8)
search - 0.2% (7)
when - 0.2% (7)
text - 0.2% (7)
using - 0.2% (7)
optimization - 0.2% (7)
\gx - 0.2% (7)
top - 0.2% (7)
sequence - 0.2% (7)
alter - 0.2% (7)
about - 0.2% (7)
used - 0.2% (7)
slash - 0.17% (6)
specified - 0.17% (6)
further - 0.17% (6)
doesn't - 0.17% (6)
implemented - 0.17% (6)
n-distinct - 0.17% (6)
give - 0.17% (6)
method - 0.17% (6)
mechanism - 0.17% (6)
being - 0.17% (6)
client - 0.17% (6)
fix - 0.17% (6)
into - 0.17% (6)
later. - 0.17% (6)
current - 0.17% (6)
only - 0.17% (6)
coefficient - 0.17% (6)
useful - 0.17% (6)
mode - 0.17% (6)
xmltable - 0.17% (6)
álvaro - 0.17% (6)
long - 0.17% (6)
me. - 0.17% (6)
file - 0.17% (6)
types - 0.17% (6)
take - 0.17% (6)
construct - 0.17% (6)
slight - 0.17% (6)
default - 0.17% (6)
clause - 0.17% (6)
replication - 0.17% (6)
prev - 0.15% (5)
sync - 0.15% (5)
stop - 0.15% (5)
processing - 0.15% (5)
perform - 0.15% (5)
jsonb - 0.15% (5)
\if - 0.15% (5)
\elif - 0.15% (5)
conditional - 0.15% (5)
expression - 0.15% (5)
under - 0.15% (5)
crash - 0.15% (5)
aka - 0.15% (5)
tom - 0.15% (5)
see - 0.15% (5)
it's - 0.15% (5)
much - 0.15% (5)
whether - 0.15% (5)
may - 0.15% (5)
query. - 0.15% (5)
adds - 0.12% (4)
always - 0.12% (4)
substitution - 0.12% (4)
boolean - 0.12% (4)
expressions - 0.12% (4)
backtick - 0.12% (4)
multiple - 0.12% (4)
logical - 0.12% (4)
such - 0.12% (4)
execute - 0.12% (4)
table, - 0.12% (4)
previous - 0.12% (4)
expansion - 0.12% (4)
hack - 0.12% (4)
feature - 0.12% (4)
tsvector - 0.12% (4)
information - 0.12% (4)
robert - 0.12% (4)
many - 0.12% (4)
file. - 0.12% (4)
"mock - 0.12% (4)
provides - 0.12% (4)
challenge - 0.12% (4)
identity - 0.12% (4)
few - 0.12% (4)
estimation - 0.12% (4)
group - 0.12% (4)
that. - 0.12% (4)
worthwhile - 0.12% (4)
special - 0.12% (4)
separate - 0.12% (4)
scripting - 0.12% (4)
write-ahead - 0.12% (4)
given - 0.12% (4)
make - 0.12% (4)
require - 0.12% (4)
seconds - 0.12% (4)
coefficients - 0.12% (4)
implementation - 0.12% (4)
alvaro - 0.12% (4)
core - 0.12% (4)
by: - 0.12% (4)
christoph - 0.12% (4)
time - 0.12% (4)
tweak - 0.12% (4)
state - 0.12% (4)
output - 0.12% (4)
introduce - 0.12% (4)
what - 0.12% (4)
explicitly - 0.12% (4)
consistency - 0.12% (4)
checking - 0.12% (4)
most - 0.12% (4)
collection - 0.12% (4)
vs. - 0.12% (4)
hash: - 0.12% (4)
amit - 0.12% (4)
slightly - 0.12% (4)
mark - 0.12% (4)
kapila - 0.12% (4)
sharma, - 0.12% (4)
ashutosh - 0.12% (4)
part - 0.12% (4)
allowing - 0.12% (4)
columns. - 0.12% (4)
bit - 0.12% (4)
yet - 0.12% (4)
server - 0.12% (4)
first - 0.12% (4)
version - 0.12% (4)
code.) - 0.12% (4)
7th - 0.12% (4)
were - 0.12% (4)
submitted - 0.12% (4)
though - 0.12% (4)
saslprep - 0.12% (4)
supported - 0.12% (4)
kyotaro - 0.12% (4)
authorization - 0.12% (4)
allows - 0.12% (4)
messages - 0.12% (4)
(rfc - 0.09% (3)
number - 0.09% (3)
5802 - 0.09% (3)
anyway - 0.09% (3)
stephen - 0.09% (3)
than - 0.09% (3)
also - 0.09% (3)
7677). - 0.09% (3)
frost - 0.09% (3)
psql: - 0.09% (3)
understood - 0.09% (3)
could - 0.09% (3)
scripting. - 0.09% (3)
performance - 0.09% (3)
linnakangas - 0.09% (3)
9th, - 0.09% (3)
later, - 0.09% (3)
they - 0.09% (3)
haas - 0.09% (3)
channel - 0.09% (3)
after - 0.09% (3)
- 0.09% (3)
password, - 0.09% (3)
\else - 0.09% (3)
\endif - 0.09% (3)
heikki - 0.09% (3)
worry - 0.09% (3)
authentication, - 0.09% (3)
it, - 0.09% (3)
these - 0.09% (3)
documentation - 0.09% (3)
help - 0.09% (3)
optimizations - 0.09% (3)
exists - 0.09% (3)
explain.depesz.com - 0.09% (3)
page - 0.09% (3)
tested - 0.06% (2)
primary> - 0.06% (2)
https://postgr.es/m/.4080608@fuzzy.cz - 0.06% (2)
series - 0.06% (2)
someone - 0.06% (2)
herrera, - 0.06% (2)
kirkwood, - 0.06% (2)
gss - 0.06% (2)
sspi - 0.06% (2)
methods. - 0.06% (2)
objects - 0.06% (2)
larger - 0.06% (2)
lack. - 0.06% (2)
cure - 0.06% (2)
types; - 0.06% (2)
indexes, - 0.06% (2)
simplicity - 0.06% (2)
kapila, - 0.06% (2)
modified - 0.06% (2)
declared - 0.06% (2)
significant - 0.06% (2)
tells - 0.06% (2)
jeff - 0.06% (2)
janes, - 0.06% (2)
8th - 0.06% (2)
varchar - 0.06% (2)
(create - 0.06% (2)
statistics), - 0.06% (2)
march, - 0.06% (2)
defined - 0.06% (2)
relational - 0.06% (2)
xml-formatted - 0.06% (2)
turning - 0.06% (2)
sql/xml - 0.06% (2)
http://postgr.es/m/cagz5qcjlerun_zoo0edv6_y_d0o4tntmper7ivtlbg4rurjdwg@mail.gmail.com - 0.06% (2)
tweaks - 0.06% (2)
https://postgr.es/m/.173334..horiguchi.kyotaro@lab.ntt.co.jp - 0.06% (2)
http://postgr.es/m/caa4ek1jobx=yu33631qh-xivyxtpsalh514+jr8xed7v+k3r_q@mail.gmail.com - 0.06% (2)
pedersen. - 0.06% (2)
jesper - 0.06% (2)
how - 0.06% (2)
checking. - 0.06% (2)
similar - 0.06% (2)
- 0.06% (2)
ghosh, - 0.06% (2)
kuntal - 0.06% (2)
form, - 0.06% (2)
usable - 0.06% (2)
noconnect - 0.06% (2)
passwordmessage - 0.06% (2)
--no-subscription-connect - 0.06% (2)
--no-create-subscription-slots - 0.06% (2)
pg_dump - 0.06% (2)
petr - 0.06% (2)
jelinek - 0.06% (2)
individual - 0.06% (2)
safe, - 0.06% (2)
exchanged - 0.06% (2)
authenticationsaslcontinue - 0.06% (2)
happens. - 0.06% (2)
syncing - 0.06% (2)
schema - 0.06% (2)
commands. - 0.06% (2)
messages. - 0.06% (2)
receiver - 0.06% (2)
owner - 0.06% (2)
obtain - 0.06% (2)
options - 0.06% (2)
several - 0.06% (2)
publications. - 0.06% (2)
companion - 0.06% (2)
combinations - 0.06% (2)
analyze - 0.06% (2)
use, - 0.06% (2)
indexes. - 0.06% (2)
old" - 0.06% (2)
explain, - 0.06% (2)
importantly, - 0.06% (2)
barring - 0.06% (2)
standbys. - 0.06% (2)
char(x) - 0.06% (2)
crash-safe - 0.06% (2)
bugs, - 0.06% (2)
"snapshot - 0.06% (2)
removed. - 0.06% (2)
support. - 0.06% (2)
logging - 0.06% (2)
mechanism-specific - 0.06% (2)
ideriha - 0.06% (2)
warning - 0.06% (2)
complex - 0.06% (2)
discouraged - 0.06% (2)
their - 0.06% (2)
19th, - 0.06% (2)
logged - 0.06% (2)
horiguchi: - 0.06% (2)
processing; - 0.06% (2)
changes - 0.06% (2)
vondra. - 0.06% (2)
tomas - 0.06% (2)
json_table, - 0.06% (2)
did - 0.06% (2)
pavel - 0.06% (2)
stehule, - 0.06% (2)
craig - 0.06% (2)
patch, - 0.06% (2)
rework - 0.06% (2)
extensively - 0.06% (2)
constructs - 0.06% (2)
approach; - 0.06% (2)
node - 0.06% (2)
executor - 0.06% (2)
relies - 0.06% (2)
specified. - 0.06% (2)
based - 0.06% (2)
hardcoded - 0.06% (2)
extensibility - 0.06% (2)
fixed, - 0.06% (2)
grammar - 0.06% (2)
(because - 0.06% (2)
ringer - 0.06% (2)
https://postgr.es/m/cafj8pragfzmd-losmnmgybd0wseznlhwap8do79+-gtrapr4qa@mail.gmail.com - 0.06% (2)
force - 0.06% (2)
resetting - 0.06% (2)
except - 0.06% (2)
exactly - 0.06% (2)
acts - 0.06% (2)
call. - 0.06% (2)
simpler - 0.06% (2)
commits - 0.06% (2)
toggle - 0.06% (2)
having - 0.06% (2)
variable, - 0.06% (2)
5th - 0.06% (2)
ensure - 0.06% (2)
mode. - 0.06% (2)
page, - 0.06% (2)
primairly - 0.06% (2)
christoph's - 0.06% (2)
often - 0.06% (2)
now, - 0.06% (2)
just - 0.06% (2)
(\x) - 0.06% (2)
álvaro. - 0.06% (2)
returned - 0.06% (2)
namespace - 0.06% (2)
currently - 0.06% (2)
said - 0.06% (2)
posts - 0.06% (2)
irc - 0.06% (2)
(the - 0.06% (2)
xmltable. - 0.06% (2)
rss - 0.06% (2)
nested - 0.06% (2)
xmlreader - 0.06% (2)
https://www.postgresql.org/message-id/20170127132737.6skslelaf4txs6iw%40msg.credativ.de">href="https://postgr.es/m/20170127132737.6skslelaf4txs6iw%40msg.credativ.de">https://www.postgresql.org/message-id/20170127132737.6skslelaf4txs6iw%40msg.credativ.de - 0.06% (2)
calls, - 0.06% (2)
xpath - 0.06% (2)
explaining - 0.06% (2)
400ms - 0.06% (2)
client-side - 0.06% (2)
unexplainable - 0.06% (2)
means - 0.06% (2)
method, - 0.06% (2)
custom - 0.06% (2)
generic - 0.06% (2)
executed - 0.06% (2)
minutes - 0.06% (2)
introduces - 0.06% (2)
reported - 0.06% (2)
rename - 0.06% (2)
pl/python). - 0.06% (2)
it; - 0.06% (2)
re-indented - 0.06% (2)
completion - 0.06% (2)
section. - 0.06% (2)
documents - 0.06% (2)
mandatory - 0.06% (2)
accept - 0.06% (2)
don't - 0.06% (2)
second, - 0.06% (2)
only. - 0.06% (2)
bit, - 0.06% (2)
https://postgr.es/m/.ixlaueanxegqd5gr@alvherre.pgsql - 0.06% (2)
berg - 0.06% (2)
requires. - 0.06% (2)
deviates - 0.06% (2)
syntax - 0.06% (2)
verite - 0.06% (2)
first, - 0.06% (2)
indicates - 0.06% (2)
input - 0.06% (2)
daniel - 0.06% (2)
optional - 0.06% (2)
passing - 0.06% (2)
benefit - 0.06% (2)
function. - 0.06% (2)
serialness - 0.06% (2)
dropping - 0.06% (2)
add/drop - 0.06% (2)
cannot - 0.06% (2)
refers - 0.06% (2)
problem - 0.06% (2)
need - 0.06% (2)
grant - 0.06% (2)
weirdnesses - 0.06% (2)
kind - 0.06% (2)
instance, - 0.06% (2)
pre-processing - 0.06% (2)
privileges - 0.06% (2)
solve. - 0.06% (2)
copies - 0.06% (2)
pseudo-type - 0.06% (2)
standard-conforming - 0.06% (2)
eisentraut - 0.06% (2)
peter - 0.06% (2)
pg_ndistinct - 0.06% (2)
variant - 0.06% (2)
postgresql's - 0.06% (2)
have: - 0.06% (2)
implemented. - 0.06% (2)
issues - 0.06% (2)
usability - 0.06% (2)
fixes - 0.06% (2)
macro - 0.06% (2)
aggregates, - 0.06% (2)
lane - 0.06% (2)
nestable - 0.06% (2)
estimate - 0.06% (2)
left - 0.06% (2)
groups - 0.06% (2)
3rd, - 0.06% (2)
sets - 0.06% (2)
blocks - 0.06% (2)
complete, - 0.06% (2)
binding, - 0.06% (2)
scram-sha-256-plus - 0.06% (2)
structure - 0.06% (2)
psql. - 0.06% (2)
essentially - 0.06% (2)
clauses; - 0.06% (2)
errors - 0.06% (2)
algorithm, - 0.06% (2)
over-allocation - 0.06% (2)
memory - 0.06% (2)
hashed - 0.06% (2)
functions - 0.06% (2)
ts_headline() - 0.06% (2)
edited - 0.06% (2)
documented - 0.06% (2)
dolgov, - 0.06% (2)
dmitry - 0.06% (2)
to_tsvector. - 0.06% (2)
trouble, - 0.06% (2)
https://www.postgresql.org/message-id/.6080106@iki.fi - 0.06% (2)
random - 0.06% (2)
value, - 0.06% (2)
system-wide - 0.06% (2)
derived - 0.06% (2)
saslprep. - 0.06% (2)
fly. - 0.06% (2)
library - 0.06% (2)
nonce", - 0.06% (2)
sufficiently - 0.06% (2)
characters, - 0.06% (2)
stored - 0.06% (2)
initdb, - 0.06% (2)
created - 0.06% (2)
authentic-looking - 0.06% (2)
constructing - 0.06% (2)
hopefully - 0.06% (2)
less - 0.06% (2)
session - 0.06% (2)
ignored. - 0.06% (2)
specification, - 0.06% (2)
functionality, - 0.06% (2)
anyway. - 0.06% (2)
itself - 0.06% (2)
"mock" - 0.06% (2)
exist, - 0.06% (2)
even - 0.06% (2)
immediately; - 0.06% (2)
through - 0.06% (2)
motions, - 0.06% (2)
haas, - 0.06% (2)
frost, - 0.06% (2)
another - 0.06% (2)
stages - 0.06% (2)
used. - 0.06% (2)
different - 0.06% (2)
david - 0.06% (2)
steele, - 0.06% (2)
https://www.postgresql.org/message-id/cab7npqrbr3gmfydedcahzukfkrgbltltmvenomprvwreszkf8g%40mail.gmail.com - 0.06% (2)
https://www.postgresql.org/message-id/cab7npqsmxu35g%3dw9x74hveqp0uvgjxvyoua4a-a3m%2b0wfebv-w%40mail.gmail.com - 0.06% (2)
others. - 0.06% (2)
alekseev, - 0.06% (2)
aleksander - 0.06% (2)
linnakangas, - 0.06% (2)
paquier - 0.06% (2)
non-ascii - 0.06% (2)
exists, - 0.06% (2)
away - 0.06% (2)
deemed - 0.06% (2)
order - 0.06% (2)
unauthenticated - 0.06% (2)
users. - 0.06% (2)
field - 0.06% (2)
michael - 0.06% (2)
(num-distinct - 0.06% (2)
pg_control_version, - 0.06% (2)
bumps - 0.06% (2)
pretty - 0.06% (2)
primitive; - 0.06% (2)
recall - 0.06% (2)
adding - 0.06% (2)
that.) - 0.06% (2)
worked - 0.06% (2)
takeshi - 0.06% (2)
remarkable - 0.06% (2)
room - 0.06% (2)
leaving - 0.06% (2)
happen. - 0.06% (2)
corey - 0.06% (2)
should - 0.06% (2)
where - 0.06% (2)
done - 0.06% (2)
(it's - 0.06% (2)
handleslashcmds. - 0.06% (2)
no-doubt-once-expedient - 0.06% (2)
mechanisms - 0.06% (2)
permitting - 0.06% (2)
kluge. - 0.06% (2)
ot_no_eval - 0.06% (2)
sometimes - 0.06% (2)
silently - 0.06% (2)
query_buf - 0.06% (2)
calling - 0.06% (2)
previous_buf - 0.06% (2)
mainloop.c's - 0.06% (2)
substituting - 0.06% (2)
huinker, - 0.06% (2)
fabien - 0.06% (2)
callback - 0.06% (2)
identities, - 0.06% (2)
provided - 0.06% (2)
source - 0.06% (2)
copying, - 0.06% (2)
internal - 0.06% (2)
works - 0.06% (2)
subscriber - 0.06% (2)
locally - 0.06% (2)
writes - 0.06% (2)
providing - 0.06% (2)
publisher - 0.06% (2)
receiving - 0.06% (2)
process. - 0.06% (2)
apply - 0.06% (2)
moment, - 0.06% (2)
between - 0.06% (2)
https://postgr.es/m/cadklm=c94osrtnat=lx0ivnq4pxdneoomffyvbkm5n_xfmltaa@mail.gmail.com - 0.06% (2)
hacking - 0.06% (2)
coelho, - 0.06% (2)
histograms - 0.06% (2)
most-common-values - 0.06% (2)
too. - 0.06% (2)
ongoing - 0.06% (2)
ddl - 0.06% (2)
designed - 0.06% (2)
replication, - 0.06% (2)
removal - 0.06% (2)
thereby - 0.06% (2)
side; - 0.06% (2)
extend - 0.06% (2)
lifting - 0.06% (2)
heavy - 0.06% (2)
since - 0.06% (2)
changing - 0.06% (2)
along - 0.06% (2)
way, - 0.06% (2)
debt - 0.06% (2)
had - 0.06% (2)
technical - 0.06% (2)
down - 0.06% (2)
pay - 0.06% (2)
purposes, - 0.06% (2)
enough - 0.06% (2)
expansion, - 0.06% (2)
result - 0.06% (2)
protocol. - 0.06% (2)
user-specified - 0.06% (2)
basically, - 0.06% (2)
"true" - 0.06% (2)
"false" - 0.06% (2)
value. - 0.06% (2)
that's - 0.06% (2)
spellings - 0.06% (2)
expressions. - 0.06% (2)
overall - 0.06% (2)
built - 0.06% (2)
around - 0.06% (2)
readable. - 0.06% (2)
teach - 0.06% (2)
seems - 0.06% (2)
overhead, - 0.06% (2)
repetitive - 0.06% (2)
header/trailer - 0.06% (2)
psql_get_variable() - 0.06% (2)
psqlscanslash.l - 0.06% (2)
stack - 0.06% (2)
state, - 0.06% (2)
basis - 0.06% (2)
future, - 0.06% (2)
suppress - 0.06% (2)
longer - 0.06% (2)
noticeably - 0.06% (2)
well - 0.06% (2)
too, - 0.06% (2)
exec_command() - 0.06% (2)
refactor - 0.06% (2)
psql/command.c: - 0.06% (2)
command, - 0.06% (2)
instead - 0.06% (2)
makes - 0.06% (2)
without - 0.06% (2)
monstrosity. - 0.06% (2)
1500-line - 0.06% (2)
tables, - 0.06% (2)
destination - 0.06% (2)
in the - 0.41% (14)
of the - 0.38% (13)
support for - 0.38% (13)
this is - 0.35% (12)
waiting for - 0.35% (12)
for postgresql - 0.32% (11)
10 – - 0.32% (11)
postgresql 10 - 0.32% (11)
| tags: - 0.29% (10)
2017 by - 0.29% (10)
depesz | - 0.29% (10)
views | - 0.29% (10)
read more - 0.29% (10)
by depesz - 0.29% (10)
and the - 0.29% (10)
more » - 0.29% (10)
» waiting - 0.26% (9)
0 comments - 0.26% (9)
committed patch: - 0.26% (9)
can be - 0.23% (8)
has been - 0.23% (8)
reviewed by - 0.23% (8)
at the - 0.23% (8)
pg10, postgresql, - 0.23% (8)
of march - 0.23% (8)
hash indexes - 0.23% (8)
on the - 0.23% (8)
comments » - 0.23% (8)
and then - 0.2% (7)
initial data - 0.2% (7)
a copy - 0.2% (7)
that i - 0.2% (7)
the same - 0.17% (6)
to use - 0.17% (6)
march 2017, - 0.17% (6)
sequence - - 0.17% (6)
this commit - 0.17% (6)
by me. - 0.17% (6)
the new - 0.17% (6)
same functionality - 0.17% (6)
to the - 0.15% (5)
use the - 0.15% (5)
and backtick - 0.12% (4)
collection of - 0.12% (4)
multivariate n-distinct - 0.12% (4)
the server - 0.12% (4)
variable substitution - 0.12% (4)
for json - 0.12% (4)
consistency checking - 0.12% (4)
functionality was - 0.12% (4)
useful to - 0.12% (4)
the control - 0.12% (4)
search support - 0.12% (4)
and jsonb - 0.12% (4)
it can - 0.12% (4)
such as - 0.12% (4)
because of - 0.12% (4)
subscription to - 0.12% (4)
be added - 0.12% (4)
commit does - 0.12% (4)
tables and - 0.12% (4)
reviewed by: - 0.12% (4)
json and - 0.12% (4)
full text - 0.12% (4)
by álvaro - 0.12% (4)
text search - 0.12% (4)
the copy - 0.12% (4)
the user - 0.12% (4)
but the - 0.12% (4)
sasl authentication - 0.12% (4)
for that - 0.12% (4)
into a - 0.12% (4)
control file. - 0.12% (4)
serial columns - 0.12% (4)
does not - 0.12% (4)
statistic types - 0.12% (4)
is used - 0.12% (4)
are added - 0.12% (4)
user doesn't - 0.12% (4)
a client - 0.12% (4)
seconds using - 0.12% (4)
added to - 0.12% (4)
is now - 0.12% (4)
ashutosh sharma, - 0.12% (4)
with a - 0.12% (4)
backtick expansion - 0.12% (4)
the sql - 0.12% (4)
amit kapila - 0.12% (4)
added later - 0.12% (4)
implement multivariate - 0.12% (4)
that it - 0.12% (4)
you can - 0.12% (4)
alvaro herrera - 0.12% (4)
query is - 0.12% (4)
n-distinct coefficients - 0.12% (4)
the current - 0.12% (4)
that the - 0.12% (4)
substitution and - 0.12% (4)
at all - 0.12% (4)
wal consistency - 0.12% (4)
no comments - 0.09% (3)
– support - 0.09% (3)
alter table - 0.09% (3)
of april - 0.09% (3)
2017, patch - 0.09% (3)
7th of - 0.09% (3)
5802 and - 0.09% (3)
authentication (rfc - 0.09% (3)
heikki linnakangas - 0.09% (3)
committed by - 0.09% (3)
support scram-sha-256 - 0.09% (3)
logical replication - 0.09% (3)
psql: add - 0.09% (3)
\gx command - 0.09% (3)
it, and - 0.09% (3)
and 7677). - 0.09% (3)
stephen frost - 0.09% (3)
be used - 0.09% (3)
in psql - 0.09% (3)
it will - 0.09% (3)
1 comment - 0.09% (3)
(rfc 5802 - 0.09% (3)
\endif in - 0.09% (3)
comments waiting - 0.09% (3)
psql scripting. - 0.09% (3)
scram-sha-256 authentication - 0.09% (3)
you will - 0.09% (3)
number of - 0.09% (3)
here to - 0.06% (2)
options were - 0.06% (2)
create and - 0.06% (2)
several new - 0.06% (2)
should happen. - 0.06% (2)
and publications. - 0.06% (2)
done explicitly - 0.06% (2)
slash commands - 0.06% (2)
obtain information - 0.06% (2)
previous query - 0.06% (2)
where that - 0.06% (2)
about tables - 0.06% (2)
worked at - 0.06% (2)
(it's a - 0.06% (2)
whether and - 0.06% (2)
calling handleslashcmds. - 0.06% (2)
query_buf when - 0.06% (2)
substituting mainloop.c's - 0.06% (2)
previous_buf for - 0.06% (2)
bit remarkable - 0.06% (2)
that commands - 0.06% (2)
that.) recall - 0.06% (2)
to control - 0.06% (2)
all with - 0.06% (2)
commands. this - 0.06% (2)
like \r - 0.06% (2)
alter subscription - 0.06% (2)
receiver can - 0.06% (2)
to have - 0.06% (2)
copy option - 0.06% (2)
new internal - 0.06% (2)
sometimes silently - 0.06% (2)
source data - 0.06% (2)
provided by - 0.06% (2)
peter eisentraut - 0.06% (2)
the copying, - 0.06% (2)
copy add - 0.06% (2)
then sync - 0.06% (2)
with the - 0.06% (2)
ongoing apply - 0.06% (2)
copy the - 0.06% (2)
functionality for - 0.06% (2)
process. for - 0.06% (2)
3rd, 2017 - 0.06% (2)
a callback - 0.06% (2)
destination table. - 0.06% (2)
that writes - 0.06% (2)
locally into - 0.06% (2)
further hacking - 0.06% (2)
fabien coelho, - 0.06% (2)
full sql - 0.06% (2)
now execute - 0.06% (2)
providing it - 0.06% (2)
the publisher - 0.06% (2)
copy works - 0.06% (2)
function. the - 0.06% (2)
discussion: https://postgr.es/m/cadklm=c94osrtnat=lx0ivnq4pxdneoomffyvbkm5n_xfmltaa@mail.gmail.com - 0.06% (2)
subscriber by - 0.06% (2)
data from - 0.06% (2)
receiving copy - 0.06% (2)
corey huinker, - 0.06% (2)
later. along - 0.06% (2)
... \else - 0.06% (2)
... \elif - 0.06% (2)
... \endif - 0.06% (2)
scripting. this - 0.06% (2)
patch adds - 0.06% (2)
me discussion: - 0.06% (2)
hacking by - 0.06% (2)
happen. corey - 0.06% (2)
that should - 0.06% (2)
huinker, reviewed - 0.06% (2)
by fabien - 0.06% (2)
coelho, further - 0.06% (2)
nestable conditional - 0.06% (2)
blocks to - 0.06% (2)
and \elif - 0.06% (2)
by \if - 0.06% (2)
are pretty - 0.06% (2)
primitive; basically, - 0.06% (2)
after variable - 0.06% (2)
expressions understood - 0.06% (2)
the boolean - 0.06% (2)
psql. the - 0.06% (2)
control structure - 0.06% (2)
feature per - 0.06% (2)
complete, but - 0.06% (2)
commands where - 0.06% (2)
the slash - 0.06% (2)
kluge. * - 0.06% (2)
the ot_no_eval - 0.06% (2)
fix the - 0.06% (2)
no-doubt-once-expedient hack - 0.06% (2)
of sometimes - 0.06% (2)
removal of - 0.06% (2)
thereby allowing - 0.06% (2)
suppress variable - 0.06% (2)
basis of - 0.06% (2)
the conditional - 0.06% (2)
stack state, - 0.06% (2)
silently substituting - 0.06% (2)
mainloop.c's previous_buf - 0.06% (2)
recall of - 0.06% (2)
with that.) - 0.06% (2)
a previous - 0.06% (2)
now done - 0.06% (2)
explicitly in - 0.06% (2)
\r worked - 0.06% (2)
commands like - 0.06% (2)
for query_buf - 0.06% (2)
when calling - 0.06% (2)
handleslashcmds. (it's - 0.06% (2)
remarkable that - 0.06% (2)
backtick expansion, - 0.06% (2)
the result - 0.06% (2)
longer because - 0.06% (2)
file noticeably - 0.06% (2)
of repetitive - 0.06% (2)
function header/trailer - 0.06% (2)
overhead, but - 0.06% (2)
makes the - 0.06% (2)
monstrosity. this - 0.06% (2)
function per - 0.06% (2)
refactor exec_command() - 0.06% (2)
command, instead - 0.06% (2)
of being - 0.06% (2)
a 1500-line - 0.06% (2)
it seems - 0.06% (2)
much more - 0.06% (2)
state, thereby - 0.06% (2)
conditional stack - 0.06% (2)
allowing removal - 0.06% (2)
ot_no_eval kluge. - 0.06% (2)
the no-doubt-once-expedient - 0.06% (2)
the basis - 0.06% (2)
expansion on - 0.06% (2)
readable. * - 0.06% (2)
teach psql_get_variable() - 0.06% (2)
and psqlscanslash.l - 0.06% (2)
to suppress - 0.06% (2)
psql/command.c: * - 0.06% (2)
up around - 0.06% (2)
value. but - 0.06% (2)
a boolean - 0.06% (2)
that's enough - 0.06% (2)
for many - 0.06% (2)
purposes, since - 0.06% (2)
spellings of - 0.06% (2)
other standard - 0.06% (2)
has to - 0.06% (2)
be "true" - 0.06% (2)
or "false" - 0.06% (2)
or one - 0.06% (2)
always do - 0.06% (2)
the heavy - 0.06% (2)
some of - 0.06% (2)
pay down - 0.06% (2)
the technical - 0.06% (2)
debt that - 0.06% (2)
had built - 0.06% (2)
the way, - 0.06% (2)
when initial - 0.06% (2)
lifting on - 0.06% (2)
side; and - 0.06% (2)
we can - 0.06% (2)
extend it - 0.06% (2)
hack of - 0.06% (2)
indexes, as - 0.06% (2)
grammar is - 0.06% (2)
(because the - 0.06% (2)
fixed, there - 0.06% (2)
extensibility in - 0.06% (2)
approach; further - 0.06% (2)
method table. - 0.06% (2)
a hardcoded - 0.06% (2)
this implementation - 0.06% (2)
be specified. - 0.06% (2)
relies on - 0.06% (2)
executor node - 0.06% (2)
based on - 0.06% (2)
constructs can - 0.06% (2)
be implemented - 0.06% (2)
stehule, álvaro - 0.06% (2)
author: pavel - 0.06% (2)
herrera extensively - 0.06% (2)
craig ringer - 0.06% (2)
discussion: https://postgr.es/m/cafj8pragfzmd-losmnmgybd0wseznlhwap8do79+-gtrapr4qa@mail.gmail.com - 0.06% (2)
core code.) - 0.06% (2)
changes to - 0.06% (2)
on top - 0.06% (2)
of this - 0.06% (2)
json_table, but - 0.06% (2)
they require - 0.06% (2)
namespace to - 0.06% (2)
a default - 0.06% (2)
first, the - 0.06% (2)
standard requires. - 0.06% (2)
standard indicates - 0.06% (2)
passing clause - 0.06% (2)
is optional - 0.06% (2)
what the - 0.06% (2)
slightly from - 0.06% (2)
using xmlreader - 0.06% (2)
5 seconds - 0.06% (2)
under pl/python). - 0.06% (2)
the implemented - 0.06% (2)
syntax deviates - 0.06% (2)
and that - 0.06% (2)
multiple xml - 0.06% (2)
single document - 0.06% (2)
accept a - 0.06% (2)
only. second, - 0.06% (2)
we don't - 0.06% (2)
currently support - 0.06% (2)
mandatory and - 0.06% (2)
make it - 0.06% (2)
input documents - 0.06% (2)
may be - 0.06% (2)
given to - 0.06% (2)
it; we - 0.06% (2)
postgresql, psql - 0.06% (2)
on 7th - 0.06% (2)
though i - 0.06% (2)
christoph's patch, - 0.06% (2)
did tweak - 0.06% (2)
the documentation - 0.06% (2)
and help - 0.06% (2)
mode. primairly - 0.06% (2)
in expanded - 0.06% (2)
it later, - 0.06% (2)
or resetting - 0.06% (2)
to ensure - 0.06% (2)
a given - 0.06% (2)
always returned - 0.06% (2)
text a - 0.06% (2)
bit, and - 0.06% (2)
explaining the - 0.06% (2)
– implement - 0.06% (2)
unexplainable – - 0.06% (2)
vs. varchar - 0.06% (2)
comments how - 0.06% (2)
discussion: - 0.06% (2)
daniel verite - 0.06% (2)
re-indented the - 0.06% (2)
tab completion - 0.06% (2)
section. author: - 0.06% (2)
christoph berg - 0.06% (2)
expanded variable, - 0.06% (2)
current state - 0.06% (2)
introduce a - 0.06% (2)
single query. - 0.06% (2)
\gx which - 0.06% (2)
acts exactly - 0.06% (2)
like \g - 0.06% (2)
just a - 0.06% (2)
(\x) for - 0.06% (2)
of march, - 0.06% (2)
often be - 0.06% (2)
use expanded - 0.06% (2)
mode output - 0.06% (2)
except that - 0.06% (2)
force expanded - 0.06% (2)
means that - 0.06% (2)
and also - 0.06% (2)
doesn't have - 0.06% (2)
to worry - 0.06% (2)
about the - 0.06% (2)
a toggle - 0.06% (2)
than having - 0.06% (2)
output mode - 0.06% (2)
one \gx - 0.06% (2)
call. this - 0.06% (2)
is simpler - 0.06% (2)
calls, and - 0.06% (2)
xpath function - 0.06% (2)
have for - 0.06% (2)
we now - 0.06% (2)
other index - 0.06% (2)
types; a - 0.06% (2)
separate patch - 0.06% (2)
psqlscanslash.l to - 0.06% (2)
for hash - 0.06% (2)
and usable - 0.06% (2)
be crash-safe - 0.06% (2)
on standbys. - 0.06% (2)
doesn't yet - 0.06% (2)
add wal - 0.06% (2)
submitted to - 0.06% (2)
cure that - 0.06% (2)
which this - 0.06% (2)
series of - 0.06% (2)
part has - 0.06% (2)
been reviewed - 0.06% (2)
and tested - 0.06% (2)
larger patch - 0.06% (2)
me. the - 0.06% (2)
lack. amit - 0.06% (2)
kapila, reviewed - 0.06% (2)
and slightly - 0.06% (2)
modified by - 0.06% (2)
will now - 0.06% (2)
barring bugs, - 0.06% (2)
for that. - 0.06% (2)
noconnect option - 0.06% (2)
author: petr - 0.06% (2)
add write-ahead - 0.06% (2)
logging support. - 0.06% (2)
subscription ... - 0.06% (2)
new create - 0.06% (2)
happens. change - 0.06% (2)
pg_dump option - 0.06% (2)
--no-create-subscription-slots to - 0.06% (2)
--no-subscription-connect and - 0.06% (2)
the warning - 0.06% (2)
about hash - 0.06% (2)
supported for - 0.06% (2)
too old" - 0.06% (2)
tables with - 0.06% (2)
hash indexes. - 0.06% (2)
most importantly, - 0.06% (2)
removed. "snapshot - 0.06% (2)
being discouraged - 0.06% (2)
indexes not - 0.06% (2)
being write-ahead - 0.06% (2)
logged and - 0.06% (2)
their use - 0.06% (2)
herrera, ashutosh - 0.06% (2)
sharma, mark - 0.06% (2)
significant simplicity - 0.06% (2)
construct provides - 0.06% (2)
and performance - 0.06% (2)
benefit for - 0.06% (2)
xml data - 0.06% (2)
this new - 0.06% (2)
a query. - 0.06% (2)
a - 0.06% (2)
used as - 0.06% (2)
primary> in - 0.06% (2)
the from - 0.06% (2)
clause of - 0.06% (2)
processing; what - 0.06% (2)
client-side custom - 0.06% (2)
(the same - 0.06% (2)
using xmltable. - 0.06% (2)
said to - 0.06% (2)
take 10 - 0.06% (2)
nested postgresql - 0.06% (2)
in 400ms - 0.06% (2)
be executed - 0.06% (2)
implementation was - 0.06% (2)
reported to - 0.06% (2)
take 20 - 0.06% (2)
minutes can - 0.06% (2)
form, so - 0.06% (2)
into relational - 0.06% (2)
and ashutosh - 0.06% (2)
kuntal ghosh, - 0.06% (2)
sharma, with - 0.06% (2)
tweaks by - 0.06% (2)
me. discussion: - 0.06% (2)
consistency checking. - 0.06% (2)
support wal - 0.06% (2)
kirkwood, jeff - 0.06% (2)
janes, and - 0.06% (2)
jesper pedersen. - 0.06% (2)
discussion: http://postgr.es/m/caa4ek1jobx=yu33631qh-xivyxtpsalh514+jr8xed7v+k3r_q@mail.gmail.com - 0.06% (2)
checking. kuntal - 0.06% (2)
ghosh, reviewed - 0.06% (2)
sql/xml standard - 0.06% (2)
by the - 0.06% (2)
feature that - 0.06% (2)
allows turning - 0.06% (2)
xml-formatted data - 0.06% (2)
is defined - 0.06% (2)
herrera committed - 0.06% (2)
by amit - 0.06% (2)
kapila and - 0.06% (2)
few tweaks - 0.06% (2)
discussion: http://postgr.es/m/cagz5qcjlerun_zoo0edv6_y_d0o4tntmper7ivtlbg4rurjdwg@mail.gmail.com - 0.06% (2)
table syncing - 0.06% (2)
"true" or - 0.06% (2)
scram-sha-256 specification, - 0.06% (2)
as specified - 0.06% (2)
are ignored. - 0.06% (2)
set session - 0.06% (2)
authorization provides - 0.06% (2)
authorization identities, - 0.06% (2)
added later. - 0.06% (2)
that does - 0.06% (2)
client library - 0.06% (2)
implement saslprep. - 0.06% (2)
that will - 0.06% (2)
hopefully be - 0.06% (2)
more or - 0.06% (2)
less the - 0.06% (2)
an authentic-looking - 0.06% (2)
by constructing - 0.06% (2)
challenge on - 0.06% (2)
the fly. - 0.06% (2)
the challenge - 0.06% (2)
"mock" authentication, - 0.06% (2)
perform a - 0.06% (2)
same functionality, - 0.06% (2)
anyway. if - 0.06% (2)
a user - 0.06% (2)
doesn't exist, - 0.06% (2)
non-ascii characters, - 0.06% (2)
password with - 0.06% (2)
the future, - 0.06% (2)
mechanisms in - 0.06% (2)
without changing - 0.06% (2)
the overall - 0.06% (2)
protocol. support - 0.06% (2)
more sasl - 0.06% (2)
allows adding - 0.06% (2)
scram-sha-256 is - 0.06% (2)
messages. only - 0.06% (2)
supported at - 0.06% (2)
the moment, - 0.06% (2)
but this - 0.06% (2)
for channel - 0.06% (2)
binding, aka - 0.06% (2)
yet implemented. - 0.06% (2)
is not - 0.06% (2)
that could - 0.06% (2)
cause trouble, - 0.06% (2)
if you - 0.06% (2)
the password, - 0.06% (2)
for pre-processing - 0.06% (2)
scram-sha-256-plus is - 0.06% (2)
left for - 0.06% (2)
later. the - 0.06% (2)
saslprep algorithm, - 0.06% (2)
is derived - 0.06% (2)
from a - 0.06% (2)
this introduces - 0.06% (2)
discussion: https://www.postgresql.org/message-id/cab7npqsmxu35g%3dw9x74hveqp0uvgjxvyoua4a-a3m%2b0wfebv-w%40mail.gmail.com - 0.06% (2)
generic sasl - 0.06% (2)
authentication method, - 0.06% (2)
similar to - 0.06% (2)
discussion: https://www.postgresql.org/message-id/cab7npqrbr3gmfydedcahzukfkrgbltltmvenomprvwreszkf8g%40mail.gmail.com - 0.06% (2)
many others. - 0.06% (2)
haas, stephen - 0.06% (2)
by robert - 0.06% (2)
frost, david - 0.06% (2)
steele, aleksander - 0.06% (2)
alekseev, and - 0.06% (2)
the gss - 0.06% (2)
and sspi - 0.06% (2)
mechanism-specific sasl - 0.06% (2)
then the - 0.06% (2)
messages are - 0.06% (2)
exchanged in - 0.06% (2)
authenticationsaslcontinue and - 0.06% (2)
use, and - 0.06% (2)
mechanism to - 0.06% (2)
methods. the - 0.06% (2)
server first - 0.06% (2)
tells the - 0.06% (2)
client which - 0.06% (2)
different stages - 0.06% (2)
reviewed at - 0.06% (2)
through these - 0.06% (2)
and stored - 0.06% (2)
motions, in - 0.06% (2)
order to - 0.06% (2)
not give - 0.06% (2)
at initdb, - 0.06% (2)
is created - 0.06% (2)
new system-wide - 0.06% (2)
random value, - 0.06% (2)
"mock authentication - 0.06% (2)
nonce", which - 0.06% (2)
away the - 0.06% (2)
information on - 0.06% (2)
file. patch - 0.06% (2)
in control - 0.06% (2)
by michael - 0.06% (2)
paquier and - 0.06% (2)
heikki linnakangas, - 0.06% (2)
new field - 0.06% (2)
pg_control_version, because - 0.06% (2)
whether the - 0.06% (2)
user exists, - 0.06% (2)
to unauthenticated - 0.06% (2)
users. bumps - 0.06% (2)
and passwordmessage - 0.06% (2)
in authenticationsaslcontinue - 0.06% (2)
too, as - 0.06% (2)
multiple tables, - 0.06% (2)
well as - 0.06% (2)
expressions. this - 0.06% (2)
commit only - 0.06% (2)
columns on - 0.06% (2)
for permitting - 0.06% (2)
multivariate histograms - 0.06% (2)
most-common-values and - 0.06% (2)
between columns - 0.06% (2)
single table, - 0.06% (2)
leaving room - 0.06% (2)
adds support - 0.06% (2)
for collection - 0.06% (2)
groups in - 0.06% (2)
of distinct - 0.06% (2)
group by - 0.06% (2)
and distinct - 0.06% (2)
clauses; estimation - 0.06% (2)
estimate number - 0.06% (2)
single table. - 0.06% (2)
of n-distinct - 0.06% (2)
coefficient on - 0.06% (2)
user-specified sets - 0.06% (2)
of columns - 0.06% (2)
as multivariate - 0.06% (2)
on, such - 0.06% (2)
objects (create - 0.06% (2)
declared statistic - 0.06% (2)
statistics), allowing - 0.06% (2)
statistics on - 0.06% (2)
more complex - 0.06% (2)
for explicitly - 0.06% (2)
add support - 0.06% (2)
will be - 0.06% (2)
19th, 2017 - 0.06% (2)
may 19th, - 0.06% (2)
tags: explain, - 0.06% (2)
comment » - 0.06% (2)
combinations that - 0.06% (2)
individual table - 0.06% (2)
too. all - 0.06% (2)
/ rename - 0.06% (2)
this ddl - 0.06% (2)
designed so - 0.06% (2)
that more - 0.06% (2)
set schema - 0.06% (2)
... owner - 0.06% (2)
columns. companion - 0.06% (2)
commands drop - 0.06% (2)
statistics and - 0.06% (2)
alter statistics - 0.06% (2)
errors there - 0.06% (2)
can cause - 0.06% (2)
ideriha takeshi - 0.06% (2)
by álvaro. - 0.06% (2)
discussion: https://postgr.es/m/.4080608@fuzzy.cz - 0.06% (2)
postgresql | - 0.06% (2)
7677). this - 0.06% (2)
code rework - 0.06% (2)
vondra. some - 0.06% (2)
though this - 0.06% (2)
horiguchi: https://postgr.es/m/.173334..horiguchi.kyotaro@lab.ntt.co.jp - 0.06% (2)
not use - 0.06% (2)
that code.) - 0.06% (2)
author: tomas - 0.06% (2)
introduces a - 0.06% (2)
new generic - 0.06% (2)
to use, - 0.06% (2)
authentication mechanism - 0.06% (2)
the mechanism-specific - 0.06% (2)
sasl messages - 0.06% (2)
are exchanged - 0.06% (2)
which sasl - 0.06% (2)
the client - 0.06% (2)
method, similar - 0.06% (2)
gss and - 0.06% (2)
sspi methods. - 0.06% (2)
first tells - 0.06% (2)
by kyotaro - 0.06% (2)
was submitted - 0.06% (2)
solve. a - 0.06% (2)
problem to - 0.06% (2)
new special - 0.06% (2)
pseudo-type pg_ndistinct - 0.06% (2)
is used. - 0.06% (2)
a worthwhile - 0.06% (2)
so it's - 0.06% (2)
over-allocation of - 0.06% (2)
memory in - 0.06% (2)
hashed aggregates, - 0.06% (2)
for instance, - 0.06% (2)
(num-distinct estimation - 0.06% (2)
was deemed - 0.06% (2)
much so - 0.06% (2)
immediately; so - 0.06% (2)
that another - 0.06% (2)
version of - 0.06% (2)
essentially the - 0.06% (2)
no further - 0.06% (2)
even if - 0.06% (2)
sufficiently useful - 0.06% (2)
by itself - 0.06% (2)
that this - 0.06% (2)
is worthwhile - 0.06% (2)
passwordmessage messages. - 0.06% (2)
only scram-sha-256 - 0.06% (2)
to_tsvector. dmitry - 0.06% (2)
ts_headline() and - 0.06% (2)
dolgov, edited - 0.06% (2)
and documented - 0.06% (2)
jsonb the - 0.06% (2)
functions are - 0.06% (2)
3 comments - 0.06% (2)
because serial - 0.06% (2)
slight weirdnesses - 0.06% (2)
is some - 0.06% (2)
kind of - 0.06% (2)
special macro - 0.06% (2)
new functions - 0.06% (2)
are ts_headline() - 0.06% (2)
\elif ... - 0.06% (2)
\if ... - 0.06% (2)
\else ... - 0.06% (2)
this patch - 0.06% (2)
adds nestable - 0.06% (2)
patch: support - 0.06% (2)
april 3rd, - 0.06% (2)
and to_tsvector. - 0.06% (2)
dmitry dolgov, - 0.06% (2)
edited and - 0.06% (2)
documented by - 0.06% (2)
- other - 0.06% (2)
to sequence - 0.06% (2)
that serial - 0.06% (2)
usability issues - 0.06% (2)
columns have: - 0.06% (2)
- create - 0.06% (2)
table / - 0.06% (2)
it fixes - 0.06% (2)
serial columns. - 0.06% (2)
some kind - 0.06% (2)
serial is - 0.06% (2)
of special - 0.06% (2)
standard-conforming variant - 0.06% (2)
of postgresql's - 0.06% (2)
like copies - 0.06% (2)
default but - 0.06% (2)
drop sequence - 0.06% (2)
dropping default - 0.06% (2)
- need - 0.06% (2)
to grant - 0.06% (2)
separate privileges - 0.06% (2)
table - - 0.06% (2)
with alter - 0.06% (2)
refers to - 0.06% (2)
same sequence - 0.06% (2)
- cannot - 0.06% (2)
add/drop serialness - 0.06% (2)
conditional blocks - 0.06% (2)
to psql. - 0.06% (2)
around psql/command.c: - 0.06% (2)
built up - 0.06% (2)
* refactor - 0.06% (2)
exec_command() into - 0.06% (2)
a function - 0.06% (2)
that had - 0.06% (2)
technical debt - 0.06% (2)
it later. - 0.06% (2)
can extend - 0.06% (2)
along the - 0.06% (2)
way, pay - 0.06% (2)
down some - 0.06% (2)
per command, - 0.06% (2)
instead of - 0.06% (2)
but it - 0.06% (2)
header/trailer overhead, - 0.06% (2)
seems much - 0.06% (2)
more readable. - 0.06% (2)
* teach - 0.06% (2)
repetitive function - 0.06% (2)
noticeably longer - 0.06% (2)
being a - 0.06% (2)
1500-line monstrosity. - 0.06% (2)
this makes - 0.06% (2)
the file - 0.06% (2)
and we - 0.06% (2)
server side; - 0.06% (2)
pretty primitive; - 0.06% (2)
\elif are - 0.06% (2)
basically, after - 0.06% (2)
expansion, the - 0.06% (2)
result has - 0.06% (2)
\if and - 0.06% (2)
understood by - 0.06% (2)
structure feature - 0.06% (2)
per se - 0.06% (2)
is complete, - 0.06% (2)
boolean expressions - 0.06% (2)
change on - 0.06% (2)
"false" or - 0.06% (2)
since you - 0.06% (2)
many purposes, - 0.06% (2)
can always - 0.06% (2)
do the - 0.06% (2)
heavy lifting - 0.06% (2)
enough for - 0.06% (2)
but that's - 0.06% (2)
one of - 0.06% (2)
the other - 0.06% (2)
standard spellings - 0.06% (2)
boolean value. - 0.06% (2)
weirdnesses because - 0.06% (2)
other slight - 0.06% (2)
session authorization - 0.06% (2)
ignored. set - 0.06% (2)
provides more - 0.06% (2)
or less - 0.06% (2)
functionality, anyway. - 0.06% (2)
specification, are - 0.06% (2)
the scram-sha-256 - 0.06% (2)
will hopefully - 0.06% (2)
saslprep. that - 0.06% (2)
later. authorization - 0.06% (2)
identities, as - 0.06% (2)
specified in - 0.06% (2)
exist, perform - 0.06% (2)
a "mock" - 0.06% (2)
value, "mock - 0.06% (2)
system-wide random - 0.06% (2)
authentication nonce", - 0.06% (2)
which is - 0.06% (2)
created at - 0.06% (2)
derived from - 0.06% (2)
challenge is - 0.06% (2)
authentication, by - 0.06% (2)
constructing an - 0.06% (2)
authentic-looking challenge - 0.06% (2)
fly. the - 0.06% (2)
does implement - 0.06% (2)
library that - 0.06% (2)
overall protocol. - 0.06% (2)
changing the - 0.06% (2)
channel binding, - 0.06% (2)
aka scram-sha-256-plus - 0.06% (2)
is left - 0.06% (2)
future, without - 0.06% (2)
sasl mechanisms - 0.06% (2)
is supported - 0.06% (2)
moment, but - 0.06% (2)
this allows - 0.06% (2)
adding more - 0.06% (2)
for later. - 0.06% (2)
the saslprep - 0.06% (2)
you use - 0.06% (2)
trouble, if - 0.06% (2)
a password - 0.06% (2)
with non-ascii - 0.06% (2)
characters, and - 0.06% (2)
could cause - 0.06% (2)
implemented. that - 0.06% (2)
algorithm, for - 0.06% (2)
pre-processing the - 0.06% (2)
password, is - 0.06% (2)
not yet - 0.06% (2)
initdb, and - 0.06% (2)
stored in - 0.06% (2)
fixes a - 0.06% (2)
columns. it - 0.06% (2)
few usability - 0.06% (2)
issues that - 0.06% (2)
have: - - 0.06% (2)
postgresql's serial - 0.06% (2)
variant of - 0.06% (2)
eisentraut committed - 0.06% (2)
2017, peter - 0.06% (2)
columns this - 0.06% (2)
is the - 0.06% (2)
sql standard-conforming - 0.06% (2)
create table - 0.06% (2)
/ like - 0.06% (2)
not drop - 0.06% (2)
default does - 0.06% (2)
need to - 0.06% (2)
grant separate - 0.06% (2)
privileges to - 0.06% (2)
- dropping - 0.06% (2)
serialness with - 0.06% (2)
copies default - 0.06% (2)
but refers - 0.06% (2)
to same - 0.06% (2)
cannot add/drop - 0.06% (2)
https://www.postgresql.org/message-id/cab7npqsmxu35g%3dw9x74hveqp0uvgjxvyoua4a-a3m%2b0wfebv-w%40mail.gmail.com discussion: - 0.06% (2)
https://www.postgresql.org/message-id/cab7npqrbr3gmfydedcahzukfkrgbltltmvenomprvwreszkf8g%40mail.gmail.com discussion: - 0.06% (2)
on whether - 0.06% (2)
the information - 0.06% (2)
exists, to - 0.06% (2)
unauthenticated users. - 0.06% (2)
bumps pg_control_version, - 0.06% (2)
give away - 0.06% (2)
to not - 0.06% (2)
file. we - 0.06% (2)
go through - 0.06% (2)
these motions, - 0.06% (2)
in order - 0.06% (2)
field in - 0.06% (2)
patch by - 0.06% (2)
david steele, - 0.06% (2)
stephen frost, - 0.06% (2)
aleksander alekseev, - 0.06% (2)
and many - 0.06% (2)
others. discussion: - 0.06% (2)
robert haas, - 0.06% (2)
stages by - 0.06% (2)
michael paquier - 0.06% (2)
and heikki - 0.06% (2)
linnakangas, reviewed - 0.06% (2)
at different - 0.06% (2)
psql_get_variable() and - 0.06% (2)
postgresql 10 – - 0.32% (11)
waiting for postgresql - 0.32% (11)
for postgresql 10 - 0.32% (11)
2017 by depesz - 0.29% (10)
by depesz | - 0.29% (10)
depesz | tags: - 0.29% (10)
read more » - 0.29% (10)
» waiting for - 0.26% (9)
more » waiting - 0.26% (9)
views | 0 - 0.26% (9)
comments » on - 0.2% (7)
of march 2017, - 0.17% (6)
initial data copy - 0.15% (5)
full text search - 0.12% (4)
variable substitution and - 0.12% (4)
substitution and backtick - 0.12% (4)
the initial data - 0.12% (4)
json and jsonb - 0.12% (4)
search support for - 0.12% (4)
support for json - 0.12% (4)
multivariate n-distinct coefficients - 0.12% (4)
implement multivariate n-distinct - 0.12% (4)
of april 2017, - 0.09% (3)
replication support for - 0.09% (3)
patch committed by - 0.09% (3)
2017, patch committed - 0.09% (3)
support scram-sha-256 authentication - 0.09% (3)
| 1 comment - 0.09% (3)
psql: add \gx - 0.09% (3)
no comments » - 0.09% (3)
in psql scripting. - 0.09% (3)
\endif in psql - 0.09% (3)
add \gx command - 0.09% (3)
(rfc 5802 and - 0.09% (3)
comments waiting for - 0.09% (3)
support for initial - 0.09% (3)
authentication (rfc 5802 - 0.09% (3)
| no comments - 0.09% (3)
for initial data - 0.09% (3)
by a callback - 0.06% (2)
can now execute - 0.06% (2)
a wal receiver - 0.06% (2)
data copy works - 0.06% (2)
full sql commands. - 0.06% (2)
function. the initial - 0.06% (2)
source data provided - 0.06% (2)
have the copy - 0.06% (2)
new options were - 0.06% (2)
and publications. several - 0.06% (2)
information about tables - 0.06% (2)
and then sync - 0.06% (2)
here to obtain - 0.06% (2)
this is used - 0.06% (2)
on the subscriber - 0.06% (2)
into a copy - 0.06% (2)
copy option to - 0.06% (2)
providing it locally - 0.06% (2)
apply process. for - 0.06% (2)
added to create - 0.06% (2)
the copying, add - 0.06% (2)
data from the - 0.06% (2)
that writes to - 0.06% (2)
the destination table. - 0.06% (2)
a new internal - 0.06% (2)
with the ongoing - 0.06% (2)
by receiving copy - 0.06% (2)
publisher and then - 0.06% (2)
--no-create-subscription-slots to --no-subscription-connect - 0.06% (2)
on standbys. this - 0.06% (2)
commit doesn't yet - 0.06% (2)
add wal consistency - 0.06% (2)
checking for hash - 0.06% (2)
crash-safe and usable - 0.06% (2)
will now be - 0.06% (2)
with hash indexes. - 0.06% (2)
most importantly, barring - 0.06% (2)
bugs, hash indexes - 0.06% (2)
indexes, as we - 0.06% (2)
now have for - 0.06% (2)
reviewed and slightly - 0.06% (2)
modified by me. - 0.06% (2)
the larger patch - 0.06% (2)
lack. amit kapila, - 0.06% (2)
to cure that - 0.06% (2)
other index types; - 0.06% (2)
a separate patch - 0.06% (2)
has been submitted - 0.06% (2)
supported for tables - 0.06% (2)
old" is now - 0.06% (2)
and use the - 0.06% (2)
new create subscription - 0.06% (2)
... noconnect option - 0.06% (2)
in the tables - 0.06% (2)
change pg_dump option - 0.06% (2)
to control whether - 0.06% (2)
and when initial - 0.06% (2)
table syncing happens. - 0.06% (2)
for that. author: - 0.06% (2)
1 comment » - 0.06% (2)
their use being - 0.06% (2)
discouraged has been - 0.06% (2)
removed. "snapshot too - 0.06% (2)
write-ahead logged and - 0.06% (2)
indexes not being - 0.06% (2)
hash: add write-ahead - 0.06% (2)
logging support. the - 0.06% (2)
warning about hash - 0.06% (2)
and alter subscription - 0.06% (2)
syncing happens. change - 0.06% (2)
should happen. corey - 0.06% (2)
huinker, reviewed by - 0.06% (2)
fabien coelho, further - 0.06% (2)
commands where that - 0.06% (2)
in the slash - 0.06% (2)
recall of a - 0.06% (2)
previous query is - 0.06% (2)
now done explicitly - 0.06% (2)
hacking by me - 0.06% (2)
3rd, 2017 by - 0.06% (2)
initial data in - 0.06% (2)
the tables and - 0.06% (2)
then sync with - 0.06% (2)
to copy the - 0.06% (2)
a new subscription - 0.06% (2)
0 comments how - 0.06% (2)
add functionality for - 0.06% (2)
all with that.) - 0.06% (2)
\r worked at - 0.06% (2)
basis of the - 0.06% (2)
conditional stack state, - 0.06% (2)
thereby allowing removal - 0.06% (2)
expansion on the - 0.06% (2)
to suppress variable - 0.06% (2)
seems much more - 0.06% (2)
readable. * teach - 0.06% (2)
psql_get_variable() and psqlscanslash.l - 0.06% (2)
of the ot_no_eval - 0.06% (2)
kluge. * fix - 0.06% (2)
calling handleslashcmds. (it's - 0.06% (2)
a bit remarkable - 0.06% (2)
that commands like - 0.06% (2)
for query_buf when - 0.06% (2)
substituting mainloop.c's previous_buf - 0.06% (2)
the no-doubt-once-expedient hack - 0.06% (2)
of sometimes silently - 0.06% (2)
the ongoing apply - 0.06% (2)
process. for the - 0.06% (2)
alter subscription to - 0.06% (2)
control whether and - 0.06% (2)
when initial table - 0.06% (2)
to create and - 0.06% (2)
options were added - 0.06% (2)
to obtain information - 0.06% (2)
about tables and - 0.06% (2)
publications. several new - 0.06% (2)
series of which - 0.06% (2)
pg_dump option --no-create-subscription-slots - 0.06% (2)
that. author: petr - 0.06% (2)
copy add functionality - 0.06% (2)
for a new - 0.06% (2)
noconnect option for - 0.06% (2)
create subscription ... - 0.06% (2)
to --no-subscription-connect and - 0.06% (2)
use the new - 0.06% (2)
is used here - 0.06% (2)
sql commands. this - 0.06% (2)
a callback function. - 0.06% (2)
copy works on - 0.06% (2)
the subscriber by - 0.06% (2)
data provided by - 0.06% (2)
the copy source - 0.06% (2)
copying, add a - 0.06% (2)
new internal copy - 0.06% (2)
option to have - 0.06% (2)
receiving copy data - 0.06% (2)
from the publisher - 0.06% (2)
destination table. a - 0.06% (2)
wal receiver can - 0.06% (2)
now execute full - 0.06% (2)
writes to the - 0.06% (2)
a copy that - 0.06% (2)
and then providing - 0.06% (2)
it locally into - 0.06% (2)
subscription to copy - 0.06% (2)
hash indexes not - 0.06% (2)
grammar is fixed, - 0.06% (2)
there is no - 0.06% (2)
extensibility in the - 0.06% (2)
table. (because the - 0.06% (2)
a hardcoded method - 0.06% (2)
implementation relies on - 0.06% (2)
a new executor - 0.06% (2)
node based on - 0.06% (2)
current approach; further - 0.06% (2)
constructs can be - 0.06% (2)
author: pavel stehule, - 0.06% (2)
álvaro herrera extensively - 0.06% (2)
reviewed by: craig - 0.06% (2)
to core code.) - 0.06% (2)
they require changes - 0.06% (2)
implemented on top - 0.06% (2)
of this such - 0.06% (2)
as json_table, but - 0.06% (2)
be specified. this - 0.06% (2)
default namespace to - 0.06% (2)
standard requires. first, - 0.06% (2)
the standard indicates - 0.06% (2)
that the passing - 0.06% (2)
from what the - 0.06% (2)
syntax deviates slightly - 0.06% (2)
and 5 seconds - 0.06% (2)
using xmlreader under - 0.06% (2)
pl/python). the implemented - 0.06% (2)
clause is optional - 0.06% (2)
and that multiple - 0.06% (2)
single document only. - 0.06% (2)
second, we don't - 0.06% (2)
currently support a - 0.06% (2)
and accept a - 0.06% (2)
make it mandatory - 0.06% (2)
xml input documents - 0.06% (2)
may be given - 0.06% (2)
to it; we - 0.06% (2)
ringer discussion: https://postgr.es/m/cafj8pragfzmd-losmnmgybd0wseznlhwap8do79+-gtrapr4qa@mail.gmail.com - 0.06% (2)
pg10, postgresql, psql - 0.06% (2)
query is always - 0.06% (2)
returned in expanded - 0.06% (2)
mode. primairly christoph's - 0.06% (2)
ensure a given - 0.06% (2)
it later, to - 0.06% (2)
the current state - 0.06% (2)
of the expanded - 0.06% (2)
variable, or resetting - 0.06% (2)
patch, though i - 0.06% (2)
did tweak the - 0.06% (2)
reviewed by: daniel - 0.06% (2)
verite discussion: - 0.06% (2)
explaining the unexplainable - 0.06% (2)
author: christoph berg - 0.06% (2)
tab completion section. - 0.06% (2)
documentation and help - 0.06% (2)
text a bit, - 0.06% (2)
and re-indented the - 0.06% (2)
to worry about - 0.06% (2)
user doesn't have - 0.06% (2)
single query. introduce - 0.06% (2)
a \gx which - 0.06% (2)
acts exactly like - 0.06% (2)
for just a - 0.06% (2)
mode output (\x) - 0.06% (2)
command it can - 0.06% (2)
often be useful - 0.06% (2)
to use expanded - 0.06% (2)
\g except that - 0.06% (2)
it will force - 0.06% (2)
having to use - 0.06% (2)
toggle and also - 0.06% (2)
means that the - 0.06% (2)
is simpler than - 0.06% (2)
\gx call. this - 0.06% (2)
expanded output mode - 0.06% (2)
for that one - 0.06% (2)
xpath function calls, - 0.06% (2)
using nested postgresql - 0.06% (2)
consistency checking for - 0.06% (2)
hash indexes, as - 0.06% (2)
we now have - 0.06% (2)
yet add wal - 0.06% (2)
this commit doesn't - 0.06% (2)
indexes will now - 0.06% (2)
be crash-safe and - 0.06% (2)
usable on standbys. - 0.06% (2)
for other index - 0.06% (2)
types; a separate - 0.06% (2)
me. the larger - 0.06% (2)
patch series of - 0.06% (2)
which this is - 0.06% (2)
slightly modified by - 0.06% (2)
kapila, reviewed and - 0.06% (2)
patch has been - 0.06% (2)
submitted to cure - 0.06% (2)
that lack. amit - 0.06% (2)
barring bugs, hash - 0.06% (2)
indexes. most importantly, - 0.06% (2)
and jesper pedersen. - 0.06% (2)
write-ahead logging support. - 0.06% (2)
the warning about - 0.06% (2)
kirkwood, jeff janes, - 0.06% (2)
ashutosh sharma, mark - 0.06% (2)
part has been - 0.06% (2)
reviewed and tested - 0.06% (2)
by álvaro herrera, - 0.06% (2)
the unexplainable – - 0.06% (2)
being write-ahead logged - 0.06% (2)
too old" is - 0.06% (2)
now supported for - 0.06% (2)
tables with hash - 0.06% (2)
been removed. "snapshot - 0.06% (2)
overhead, but it - 0.06% (2)
and their use - 0.06% (2)
being discouraged has - 0.06% (2)
a part has - 0.06% (2)
been reviewed and - 0.06% (2)
construct provides significant - 0.06% (2)
simplicity and performance - 0.06% (2)
benefit for xml - 0.06% (2)
query. this new - 0.06% (2)
clause of a - 0.06% (2)
be used as - 0.06% (2)
a - 0.06% (2)
in the from - 0.06% (2)
data processing; what - 0.06% (2)
in a client-side - 0.06% (2)
(the same functionality - 0.06% (2)
was said to - 0.06% (2)
take 10 seconds - 0.06% (2)
400ms using xmltable. - 0.06% (2)
be executed in - 0.06% (2)
custom implementation was - 0.06% (2)
reported to take - 0.06% (2)
20 minutes can - 0.06% (2)
that it can - 0.06% (2)
relational form, so - 0.06% (2)
hash: support wal - 0.06% (2)
consistency checking. kuntal - 0.06% (2)
ghosh, reviewed by - 0.06% (2)
pedersen. discussion: http://postgr.es/m/caa4ek1jobx=yu33631qh-xivyxtpsalh514+jr8xed7v+k3r_q@mail.gmail.com - 0.06% (2)
janes, and jesper - 0.06% (2)
tested by álvaro - 0.06% (2)
herrera, ashutosh sharma, - 0.06% (2)
mark kirkwood, jeff - 0.06% (2)
amit kapila and - 0.06% (2)
ashutosh sharma, with - 0.06% (2)
as a feature - 0.06% (2)
that allows turning - 0.06% (2)
xml-formatted data into - 0.06% (2)
the sql/xml standard - 0.06% (2)
is defined by - 0.06% (2)
a few tweaks - 0.06% (2)
by me. discussion: - 0.06% (2)
this is a - 0.06% (2)
later. along the - 0.06% (2)
you use a - 0.06% (2)
password with non-ascii - 0.06% (2)
characters, and a - 0.06% (2)
cause trouble, if - 0.06% (2)
implemented. that could - 0.06% (2)
saslprep algorithm, for - 0.06% (2)
pre-processing the password, - 0.06% (2)
is not yet - 0.06% (2)
client library that - 0.06% (2)
does implement saslprep. - 0.06% (2)
ignored. set session - 0.06% (2)
authorization provides more - 0.06% (2)
or less the - 0.06% (2)
scram-sha-256 specification, are - 0.06% (2)
specified in the - 0.06% (2)
that will hopefully - 0.06% (2)
be added later. - 0.06% (2)
authorization identities, as - 0.06% (2)
for later. the - 0.06% (2)
scram-sha-256-plus is left - 0.06% (2)
then the mechanism-specific - 0.06% (2)
sasl messages are - 0.06% (2)
exchanged in authenticationsaslcontinue - 0.06% (2)
to use, and - 0.06% (2)
sasl authentication mechanism - 0.06% (2)
sspi methods. the - 0.06% (2)
server first tells - 0.06% (2)
the client which - 0.06% (2)
and passwordmessage messages. - 0.06% (2)
only scram-sha-256 is - 0.06% (2)
changing the overall - 0.06% (2)
protocol. support for - 0.06% (2)
channel binding, aka - 0.06% (2)
the future, without - 0.06% (2)
sasl mechanisms in - 0.06% (2)
supported at the - 0.06% (2)
moment, but this - 0.06% (2)
allows adding more - 0.06% (2)
same functionality, anyway. - 0.06% (2)
if a user - 0.06% (2)
paquier and heikki - 0.06% (2)
linnakangas, reviewed at - 0.06% (2)
different stages by - 0.06% (2)
patch by michael - 0.06% (2)
in control file. - 0.06% (2)
unauthenticated users. bumps - 0.06% (2)
pg_control_version, because of - 0.06% (2)
the new field - 0.06% (2)
robert haas, stephen - 0.06% (2)
frost, david steele, - 0.06% (2)
the sql standard-conforming - 0.06% (2)
variant of postgresql's - 0.06% (2)
serial columns. it - 0.06% (2)
columns this is - 0.06% (2)
2017, peter eisentraut - 0.06% (2)
aleksander alekseev, and - 0.06% (2)
many others. discussion: - 0.06% (2)
https://www.postgresql.org/message-id/cab7npqrbr3gmfydedcahzukfkrgbltltmvenomprvwreszkf8g%40mail.gmail.com discussion: https://www.postgresql.org/message-id/cab7npqsmxu35g%3dw9x74hveqp0uvgjxvyoua4a-a3m%2b0wfebv-w%40mail.gmail.com - 0.06% (2)
user exists, to - 0.06% (2)
on whether the - 0.06% (2)
challenge is derived - 0.06% (2)
from a new - 0.06% (2)
system-wide random value, - 0.06% (2)
the fly. the - 0.06% (2)
authentic-looking challenge on - 0.06% (2)
doesn't exist, perform - 0.06% (2)
a "mock" authentication, - 0.06% (2)
by constructing an - 0.06% (2)
"mock authentication nonce", - 0.06% (2)
which is created - 0.06% (2)
motions, in order - 0.06% (2)
to not give - 0.06% (2)
away the information - 0.06% (2)
go through these - 0.06% (2)
control file. we - 0.06% (2)
at initdb, and - 0.06% (2)
stored in the - 0.06% (2)
the gss and - 0.06% (2)
method, similar to - 0.06% (2)
between columns of - 0.06% (2)
a single table, - 0.06% (2)
leaving room for - 0.06% (2)
and multivariate histograms - 0.06% (2)
as multivariate most-common-values - 0.06% (2)
more statistic types - 0.06% (2)
can be added - 0.06% (2)
later on, such - 0.06% (2)
permitting columns on - 0.06% (2)
multiple tables, too, - 0.06% (2)
user-specified sets of - 0.06% (2)
columns in a - 0.06% (2)
single table. this - 0.06% (2)
n-distinct coefficient on - 0.06% (2)
for collection of - 0.06% (2)
as well as - 0.06% (2)
expressions. this commit - 0.06% (2)
only adds support - 0.06% (2)
designed so that - 0.06% (2)
ddl has been - 0.06% (2)
for explicitly declared - 0.06% (2)
statistic objects (create - 0.06% (2)
statistics), allowing collection - 0.06% (2)
coefficients add support - 0.06% (2)
herrera committed patch: - 0.06% (2)
| tags: explain, - 0.06% (2)
10 – implement - 0.06% (2)
may 19th, 2017 - 0.06% (2)
of statistics on - 0.06% (2)
more complex combinations - 0.06% (2)
set schema / - 0.06% (2)
rename are added - 0.06% (2)
too. all this - 0.06% (2)
owner to / - 0.06% (2)
alter statistics ... - 0.06% (2)
that individual table - 0.06% (2)
columns. companion commands - 0.06% (2)
drop statistics and - 0.06% (2)
is useful to - 0.06% (2)
estimate number of - 0.06% (2)
https://postgr.es/m/.173334..horiguchi.kyotaro@lab.ntt.co.jp though this - 0.06% (2)
commit does not - 0.06% (2)
use that code.) - 0.06% (2)
by kyotaro horiguchi: - 0.06% (2)
functionality was submitted - 0.06% (2)
much so that - 0.06% (2)
another version of - 0.06% (2)
essentially the same - 0.06% (2)
author: tomas vondra. - 0.06% (2)
some code rework - 0.06% (2)
and 7677). this - 0.06% (2)
introduces a new - 0.06% (2)
generic sasl authentication - 0.06% (2)
» on 7th - 0.06% (2)
committed by alvaro - 0.06% (2)
by álvaro. ideriha - 0.06% (2)
takeshi discussion: https://postgr.es/m/.4080608@fuzzy.cz - 0.06% (2)
by alvaro herrera - 0.06% (2)
added immediately; so - 0.06% (2)
statistic types are - 0.06% (2)
memory in hashed - 0.06% (2)
aggregates, for instance, - 0.06% (2)
so it's a - 0.06% (2)
cause over-allocation of - 0.06% (2)
errors there can - 0.06% (2)
distinct groups in - 0.06% (2)
group by and - 0.06% (2)
distinct clauses; estimation - 0.06% (2)
worthwhile problem to - 0.06% (2)
solve. a new - 0.06% (2)
itself that this - 0.06% (2)
is worthwhile even - 0.06% (2)
if no further - 0.06% (2)
sufficiently useful by - 0.06% (2)
estimation was deemed - 0.06% (2)
special pseudo-type pg_ndistinct - 0.06% (2)
is used. (num-distinct - 0.06% (2)
fixes a few - 0.06% (2)
usability issues that - 0.06% (2)
like \r worked - 0.06% (2)
at all with - 0.06% (2)
that.) recall of - 0.06% (2)
remarkable that commands - 0.06% (2)
(it's a bit - 0.06% (2)
silently substituting mainloop.c's - 0.06% (2)
previous_buf for query_buf - 0.06% (2)
when calling handleslashcmds. - 0.06% (2)
a previous query - 0.06% (2)
is now done - 0.06% (2)
further hacking by - 0.06% (2)
\if ... \elif - 0.06% (2)
... \else ... - 0.06% (2)
by fabien coelho, - 0.06% (2)
corey huinker, reviewed - 0.06% (2)
explicitly in the - 0.06% (2)
slash commands where - 0.06% (2)
that should happen. - 0.06% (2)
hack of sometimes - 0.06% (2)
fix the no-doubt-once-expedient - 0.06% (2)
noticeably longer because - 0.06% (2)
of repetitive function - 0.06% (2)
header/trailer overhead, but - 0.06% (2)
makes the file - 0.06% (2)
1500-line monstrosity. this - 0.06% (2)
into a function - 0.06% (2)
per command, instead - 0.06% (2)
of being a - 0.06% (2)
it seems much - 0.06% (2)
more readable. * - 0.06% (2)
state, thereby allowing - 0.06% (2)
removal of the - 0.06% (2)
ot_no_eval kluge. * - 0.06% (2)
the conditional stack - 0.06% (2)
the basis of - 0.06% (2)
teach psql_get_variable() and - 0.06% (2)
psqlscanslash.l to suppress - 0.06% (2)
backtick expansion on - 0.06% (2)
scripting. this patch - 0.06% (2)
adds nestable conditional - 0.06% (2)
new change on - 0.06% (2)
way, pay down - 0.06% (2)
some of the - 0.06% (2)
can extend it - 0.06% (2)
side; and we - 0.06% (2)
can always do - 0.06% (2)
the heavy lifting - 0.06% (2)
on the server - 0.06% (2)
technical debt that - 0.06% (2)
had built up - 0.06% (2)
monstrosity. this makes - 0.06% (2)
the file noticeably - 0.06% (2)
longer because of - 0.06% (2)
being a 1500-line - 0.06% (2)
command, instead of - 0.06% (2)
around psql/command.c: * - 0.06% (2)
refactor exec_command() into - 0.06% (2)
a function per - 0.06% (2)
purposes, since you - 0.06% (2)
enough for many - 0.06% (2)
understood by \if - 0.06% (2)
and \elif are - 0.06% (2)
pretty primitive; basically, - 0.06% (2)
the boolean expressions - 0.06% (2)
is complete, but - 0.06% (2)
blocks to psql. - 0.06% (2)
the control structure - 0.06% (2)
feature per se - 0.06% (2)
after variable substitution - 0.06% (2)
and backtick expansion, - 0.06% (2)
other standard spellings - 0.06% (2)
of a boolean - 0.06% (2)
value. but that's - 0.06% (2)
one of the - 0.06% (2)
or "false" or - 0.06% (2)
the result has - 0.06% (2)
to be "true" - 0.06% (2)
* refactor exec_command() - 0.06% (2)
up around psql/command.c: - 0.06% (2)
refers to same - 0.06% (2)
sequence - cannot - 0.06% (2)
add/drop serialness with - 0.06% (2)
copies default but - 0.06% (2)
table / like - 0.06% (2)
few usability issues - 0.06% (2)
that serial columns - 0.06% (2)
have: - create - 0.06% (2)
alter table - - 0.06% (2)
dropping default does - 0.06% (2)
because serial is - 0.06% (2)
some kind of - 0.06% (2)
– full text - 0.06% (2)
other slight weirdnesses - 0.06% (2)
to sequence - - 0.06% (2)
not drop sequence - 0.06% (2)
- need to - 0.06% (2)
grant separate privileges - 0.06% (2)
it fixes a - 0.06% (2)
postgresql's serial columns. - 0.06% (2)
- cannot add/drop - 0.06% (2)
serialness with alter - 0.06% (2)
table - dropping - 0.06% (2)
to same sequence - 0.06% (2)
default but refers - 0.06% (2)
serial columns have: - 0.06% (2)
- create table - 0.06% (2)
/ like copies - 0.06% (2)
default does not - 0.06% (2)
drop sequence - - 0.06% (2)
kind of special - 0.06% (2)
is the sql - 0.06% (2)
standard-conforming variant of - 0.06% (2)
serial is some - 0.06% (2)
slight weirdnesses because - 0.06% (2)
need to grant - 0.06% (2)
separate privileges to - 0.06% (2)
sequence - other - 0.06% (2)
| 3 comments - 0.06% (2)
the new functions - 0.06% (2)
boolean value. but - 0.06% (2)
that's enough for - 0.06% (2)
many purposes, since - 0.06% (2)
spellings of a - 0.06% (2)
the other standard - 0.06% (2)
has to be - 0.06% (2)
"true" or "false" - 0.06% (2)
or one of - 0.06% (2)
you can always - 0.06% (2)
do the heavy - 0.06% (2)
down some of - 0.06% (2)
the technical debt - 0.06% (2)
that had built - 0.06% (2)
the way, pay - 0.06% (2)
it later. along - 0.06% (2)
lifting on the - 0.06% (2)
server side; and - 0.06% (2)
we can extend - 0.06% (2)
expansion, the result - 0.06% (2)
basically, after variable - 0.06% (2)
\elif ... \else - 0.06% (2)
... \endif in - 0.06% (2)
psql scripting. this - 0.06% (2)
support \if ... - 0.06% (2)
april 3rd, 2017 - 0.06% (2)
are ts_headline() and - 0.06% (2)
to_tsvector. dmitry dolgov, - 0.06% (2)
edited and documented - 0.06% (2)
patch adds nestable - 0.06% (2)
conditional blocks to - 0.06% (2)
expressions understood by - 0.06% (2)
\if and \elif - 0.06% (2)
are pretty primitive; - 0.06% (2)
but the boolean - 0.06% (2)
se is complete, - 0.06% (2)
psql. the control - 0.06% (2)
structure feature per - 0.06% (2)
repetitive function header/trailer - 0.06% (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.