On Thu, Dec 1, 2011 at 12:30 AM, Robert Haas robertmh...@gmail.com wrote:
On Mon, Nov 21, 2011 at 11:49 AM, Alexander Korotkov
aekorot...@gmail.com wrote:
I've a question about pg_mb2wchar function. Is there any way for inverse
convertion pg_wchar* to char*?
I've looked to pg_wchar_tbl
On Thu, Dec 1, 2011 at 12:29 AM, Robert Haas robertmh...@gmail.com wrote:
Please add this patch here so it does not get lost in the shuffle:
https://commitfest.postgresql.org/action/commitfest_view/open
Done.
--
With best regards,
Alexander Korotkov.
Excerpts from Alexander Shulgin's message of Sat Nov 26 21:46:32 +0200 2011:
I would also think that if one is to specify the password in the URI, and the
password happen to contain the @-sign (e.g. !@#$%^,) it should be
percent-encoded, like:
postgresql://user:!%40#$%^@/
Actually
Excerpts from Alexander Shulgin's message of Sat Nov 26 22:07:21 +0200 2011:
So how about this:
postgresql:ssl://user:pw@host:port/dbname?sslmode=...
The postgresql:ssl:// designator would assume sslmode=require, if not
overriden in extra parameters and postgresql:// would imply
Excerpts from Greg Smith's message of Mon Nov 28 10:08:42 +0200 2011:
On 11/24/2011 05:21 AM, Alvaro Herrera wrote:
A coworker also suggested using a different designator:
postgresqli:///path/to/socket:5433/database
postgresqli://:5433/database
This is not unprecedented. An example
On Sat, Nov 26, 2011 at 11:11 AM, Jeff Davis pg...@j-davis.com wrote:
There's been some significant change in rangetypes_gist.c, can you
please rebase this patch?
OK, rebased with head.
--
With best regards,
Alexander Korotkov.
rangetypegist-0.3.patch.gz
Description: GNU Zip compressed
is solved by introduction of RANGE_CONTAIN_EMPTY
bit in range flags. This bit is only used in GiST index and means that
there are underlying empty ranges.
--
With best regards,
Alexander Korotkov.
list:
http://wiki.postgresql.org/wiki/Foreign_data_wrappers
Is there any procedure for it?
On Thu, Sep 29, 2011 at 1:20 AM, Kevin Grittner
kevin.gritt...@wicourts.gov wrote:
Florian Pflug f...@phlo.org wrote:
On Sep28, 2011, at 15:32 , Alexander Soudakov wrote:
Here you can find www_fdw feature
PM, Alexander Soudakov cyga...@gmail.com wrote:
Hello.
I finished developing www_fdw:
https://github.com/cyga/www_fdw/
It has docs/examples:
https://github.com/cyga/www_fdw/wiki
I haven't upload it to pgxn or pgfoundry yet.
I want to ask for the following 2 things:
1. testing from
. The redesign of the penalty and picksplit
functions should be discussed separately.
I think the same.
--
With best regards,
Alexander Korotkov.
met
recommendation to choose smallest box from boxes with same extention (it's
not a rare situation to have multiple boxes with zero extention) for tuple
insertion. But with current interface, we can't implement it.
--
With best regards,
Alexander Korotkov.
Excerpts from Peter Eisentraut's message of Thu Nov 24 22:05:09 +0200 2011:
On tor, 2011-11-24 at 15:43 +0200, Alexander Shulgin wrote:
Huh? The service definitions are read from a local pg_service.conf,
and are specified by setting PGSERVICE (and PGSERVICEFILE) environment
variables
Excerpts from Robert Haas's message of Thu Nov 24 15:59:08 +0200 2011:
I think we could do something like:
postgresql://user:pw@host:port/database?param1=val1param2=val2param3=val3...
I wonder if this should be allowed syntax (i.e. specify a user, but connect
locally, so leave 'host' to
Excerpts from Robert Haas's message of Thu Nov 24 13:57:17 +0200 2011:
I think it would be really weird not to support user:pw@host:port. You can
presumably also support the JDBC style for backward compatibility, but I
don't think we should adopt that syntax as project standard.
By the
Excerpts from Martijn van Oosterhout's message of Thu Nov 24 09:40:42 +0200
2011:
On Thu, Nov 24, 2011 at 08:59:56AM +0200, Alexander Shulgin wrote:
How would you specifiy a local port/UNIX domain socket?
Missed that in my previous reply.
If host part of the URI points to localhost
Excerpts from Florian Weimer's message of Thu Nov 24 11:27:51 +0200 2011:
and why you don't use bytea ? Text should be correct literal.
It's actually UTF-8 text, and some PostgreSQL functions are only
available for TEXT, but not BYTEA, e.g.:
bfk_int= SELECT '\x006500'::bytea ~ 'A';
Excerpts from Florian Weimer's message of Thu Nov 24 12:59:09 +0200 2011:
I have a different question. What is reason for embedded NULs inside
strings?
The source system does not enforce that constraint, so from time to
time, such data slips through. I don't know why it's there in the
Excerpts from Robert Haas's message of Thu Nov 24 13:57:17 +0200 2011:
I think it would be really weird not to support user:pw@host:port. You can
presumably also support the JDBC style for backward compatibility, but I
don't think we should adopt that syntax as project standard.
Well, I
Excerpts from Alvaro Herrera's message of Thu Nov 24 15:21:49 +0200 2011:
I think the question is allowing the URI to specify a service.
Huh? The service definitions are read from a local pg_service.conf, and are
specified by setting PGSERVICE (and PGSERVICEFILE) environment variables, no?
Excerpts from Robert Haas's message of Thu Nov 24 15:35:36 +0200 2011:
Do you suggest that we should reconsider?
I guess my feeling is that if we're going to have URLs, we ought to
try to adhere to the same conventions that are used for pretty much
every other service that supports URLs.
Excerpts from Robert Haas's message of Thu Nov 24 15:59:08 +0200 2011:
Well, based on that document, I think that trying to be bug-compatible
with the JDBC syntax is a, erm, doomed effort. I mean, what are you
going to do with things like loglevel or logUnclosedConnections that
change the
Excerpts from Alexey Klyukin's message of Thu Nov 24 10:22:21 +0200 2011:
Another idea is to use local:/dir/name for UNIX domain socket instead of
hostname:port, like it's displayed in the psql prompt.
So the whole thing would look like this:
Excerpts from Robert Haas's message of Thu Nov 24 16:02:38 +0200 2011:
So, in that light, do we still think that letting the user specify a
service name in the URI makes sense? (My personal opinion is yes).
service is just a connection parameter, so if we choose a URL format
that
Excerpts from Florian Weimer's message of Thu Nov 24 16:31:29 +0200 2011:
I plan to add UNIX Domain socket support to the JDBC driver.
Eventually, the JDK will expose UNIX Domain sockets to Java code, too
(they are already used internally for management functions).
Do you maybe plan to
Excerpts from Robert Haas's message of Thu Nov 24 17:02:13 +0200 2011:
On Thu, Nov 24, 2011 at 9:40 AM, Alexander Shulgin
a...@commandprompt.com wrote:
Another idea is to use local:/dir/name for UNIX domain socket instead of
hostname:port, like it's displayed in the psql prompt.
So
Excerpts from Florian Weimer's message of Wed Nov 23 13:04:47 +0200 2011:
* Alexander Shulgin:
This, in my opinion, is very similar to what we would like to achieve with
the URI syntax, so the above could also be specified using a URI parameter
like this:
psql -d postgresql
Excerpts from Florian Weimer's message of Wed Nov 23 13:04:47 +0200 2011:
* Alexander Shulgin:
This, in my opinion, is very similar to what we would like to achieve with
the URI syntax, so the above could also be specified using a URI parameter
like this:
psql -d postgresql
Excerpts from Dmitriy Igrishin's message of Thu Nov 24 09:19:02 +0200 2011:
If host part of the URI points to localhost, the UNIX domain socket would
be considered by libpq just as if you would pass -h localhost -p 5433.
But what if the user wants to connect exactly via socket or
TCP/IP
hardcoded some dirty solution. So
PG_EUC_JP, PG_EUC_CN, PG_EUC_KR, PG_EUC_TW, PG_EUC_JIS_2004 are not
supported yet.
--
With best regards,
Alexander Korotkov.
trgm-regexp-0.1.patch.gz
Description: GNU Zip compressed data
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make
for regexp search and I'm trying to
get some characters back from color map.
--
With best regards,
Alexander Korotkov.
Hello,
It was proposed a while ago for libpq to support URI syntax for specifying the
connection information:
http://archives.postgresql.org/message-id/1302114698.23164.17.camel@jd-desktop
http://archives.postgresql.org/pgsql-hackers/2011-07/msg01144.php
It appears to me that the
Hello Hackers.
I attached trivial patch.
Foreign table either defines row type. I simply added this type to
hardcoded check.
I faced this limitation while developing www fdw feature
(http://wiki.postgresql.org/wiki/WWW_FDW).
--
Alexander Soudakov
Software Developer
email: cyga...@gmail.com
Rebased with head.
--
With best regards,
Alexander Korotkov.
arrayanalyze-0.7.patch.gz
Description: GNU Zip compressed data
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
estimations with lower selectivity, which make planner
use corresponding index by default (like we've for geometric datatypes).
--
With best regards,
Alexander Korotkov.
.
So, !? and ? operators are mentioned in documentation, but don't present in
catalog. Are them just missed in the catalog or there is some more serious
problem?
--
With best regards,
Alexander Korotkov.
First version of GiST for range types patch is here. Comments refactoring
testing are coming soon.
--
With best regards,
Alexander Korotkov.
rangetypegist-0.1.patch.gz
Description: GNU Zip compressed data
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make
doesn't store positions too. See gtsvector_compress. It converts
tsvector to array of crc32 of words. If that value is anyway too large then
function converts it to signature.
--
With best regards,
Alexander Korotkov.
as a separate
patch.
Cool! Patch with GiST on range types improvements from me will be soon.
--
With best regards,
Alexander Korotkov.
On Mon, Oct 24, 2011 at 3:05 PM, Alexander Korotkov aekorot...@gmail.comwrote:
If we allow user to specify own gist_penalty function, then such function
should deal with:
1) GiST-specific data structures such as GISTENTRY.
2) Decomposing ranges using range_deserialize.
3) Inifinities, which
range_deserialize.
3) Inifinities, which we could handle in general penalty functions.
Thats why I prefere to implement subtype_diff.
--
With best regards,
Alexander Korotkov.
,
Alexander Korotkov.
On Tue, Oct 25, 2011 at 1:46 AM, Kevin Grittner kevin.gritt...@wicourts.gov
wrote:
Alexander Korotkov aekorot...@gmail.com wrote:
Coundn't be predicate locking implementation in SSI be used for
in-database cache invalidation.
It would not necessarily be limited to *in-database* caches
Hi!
Thanks for your attention to my patch!
On Sat, Oct 15, 2011 at 2:47 PM, Nathan Boley npbo...@gmail.com wrote:
Looking now, I see that Alexander wasn't Cc'd on the review, so it's
possible he missed the message?
We've corresponded off list and have discussed my review at some length
regards,
Alexander Korotkov.
function? There are
situations when restoring of original tuple requires some transformation.
For example, in point_ops we store box in the leaf index tuple, while point
can be easily restored from box.
--
With best regards,
Alexander Korotkov.
multiple opclasses, AM API function should also say *what* data index can
return.
--
With best regards,
Alexander Korotkov.
On Sat, Oct 8, 2011 at 1:01 PM, Jeff Davis pg...@j-davis.com wrote:
On Fri, 2011-10-07 at 12:54 +0400, Alexander Korotkov wrote:
The first thing caught my eye in existing GiST code is idea of
subtype_float. float8 has limited precision and can't respresent, for
example, varlena values
values of subtype as an float? Using of such
function could make penalty more sensible to even small difference between
values, and accordingly more relevant.
--
With best regards,
Alexander Korotkov.
On Thu, Oct 6, 2011 at 11:06 AM, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
On 05.10.2011 15:59, Alexander Korotkov wrote:
Path without allocating extra bytes is attached.
I run some more detailed tests on geonames and two smaller datasets from
rtreeportal.org.
Ok
efficient on highly overlapping ranges than current picksplit.
Range types patch isn't commited, yet. So, what way of work publishing is
prefered in this case? Add-on patch, separate branch in git or something
else?
--
With best regards,
Alexander Korotkov.
On Wed, Oct 5, 2011 at 11:37 AM, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
On 04.10.2011 15:10, Alexander Korotkov wrote:
On Tue, Oct 4, 2011 at 1:46 PM, Heikki Linnakangas
heikki.linnakangas@**enterprisedb.comheikki.linnakan...@enterprisedb.com
wrote:
Ok. Could you
the
presented cases. Difference in test2 and test3 is not so big as it is in
test1. It can be explained by fact that test2 and test3 are smaller than
test1.
--
With best regards,
Alexander Korotkov.
scripts.tar.gz
Description: GNU Zip compressed data
*** a/src/backend/access/gist/gistproc.c
--- b
regards,
Alexander Korotkov.
. to
hopefully make it more readable.
Thanks for your work on this patch. Patch with comment is attached.
--
With best regards,
Alexander Korotkov.
*** a/src/backend/access/gist/gistproc.c
--- b/src/backend/access/gist/gistproc.c
***
*** 26,31 static bool gist_box_leaf_consistent(BOX *key
On Thu, Sep 29, 2011 at 1:20 AM, Kevin Grittner
kevin.gritt...@wicourts.gov wrote:
Florian Pflug f...@phlo.org wrote:
On Sep28, 2011, at 15:32 , Alexander Soudakov wrote:
Here you can find www_fdw feature documentation:
http://wiki.postgresql.org/wiki/WWW_FDW
Certainly looks useful
signature of newitem in gtrgm_penalty
like gtrgm_consistent do this for query?
--
With best regards,
Alexander Korotkov.
that instead of micro-optimizing makesign.
GiST for tsearch works similarly.
--
With best regards,
Alexander Korotkov.
procedure outline and output below. Your patch
behaves as you described in the email containing 'v5' and judging by
Andy's earlier success, I think this is ready to go. I will mark this
'Ready for Committer'.
Alexander
---
TESTING METHODOLOGY
===
* Start postgres
Greetings postgres hackers!
Here you can find www_fdw feature documentation:
http://wiki.postgresql.org/wiki/WWW_FDW
Looking forward for your feedback.
--
Alexander Soudakov
Developer Programmer
email: cyga...@gmail.com
skype: asudakov
--
Sent via pgsql-hackers mailing list (pgsql-hackers
On Wed, Sep 28, 2011 at 7:17 PM, David Fetter da...@fetter.org wrote:
On Wed, Sep 28, 2011 at 05:32:37PM +0400, Alexander Soudakov wrote:
Greetings postgres hackers!
Here you can find www_fdw feature documentation:
http://wiki.postgresql.org/wiki/WWW_FDW
Looking forward for your feedback
inline
On Wed, Sep 28, 2011 at 7:21 PM, Andrew Dunstan and...@dunslane.net wrote:
On 09/28/2011 09:32 AM, Alexander Soudakov wrote:
Greetings postgres hackers!
Here you can find www_fdw feature documentation:
http://wiki.postgresql.org/wiki/WWW_FDW
Looking forward for your feedback
nodes can be packed into single
page. Thereby it would be interesting to compare also CPU load GiST
vs. SP-GiST. Also, there is some hope to reduce number of page accesses in
SP-GiST by improving clustering algorithm.
--
With best regards,
Alexander Korotkov.
, or is there something missing that should be
using them?
Yes, it's just dead code.
--
With best regards,
Alexander Korotkov.
On Thu, Sep 22, 2011 at 3:31 PM, Alexander Korotkov aekorot...@gmail.comwrote:
On Thu, Sep 22, 2011 at 3:22 PM, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
'lower' and 'upper' are not used for anything in the above. Is that just
dead code that can be removed
of
pages accesse is presented in dependency of table, buffering build and split
method.
Note, that tests were run with not last version of fast build patch
(gist_fast_build-heikki-0.14.1.1.patch was used). Therefore, build time
with buffering can be better.
--
With best regards,
Alexander Korotkov
On Fri, Sep 16, 2011 at 3:07 PM, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
That looks awfully complicated. I don't understand how that works. I wonder
if two passes would be simpler?
I doubt it becomes much simpler, but here it is.
--
With best regards,
Alexander
.
--
With best regards,
Alexander Korotkov.
of
interval.
--
With best regards,
Alexander Korotkov.
/spgist.
* Signature indexing with gist/spgist in various fields. For example,
indexing of image signatures with similar images retreival.
* Statistics collection and selectivity estimation for geometric datatypes.
--
With best regards,
Alexander Korotkov.
)
--
With best regards,
Alexander Korotkov.
double-sorting-split-0.1.patch.gz
Description: GNU Zip compressed data
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Thanks for congratulations!
Tnanks to Heikki for mentoring and his work on patch!
--
With best regards,
Alexander Korotkov.
discussing in this thread GiST build can win form unlogged as
much as with regular build.
--
With best regards,
Alexander Korotkov.
missing something)
For the queries you mentioned you may see LIKE acceleration in wildspeed
module (http://www.sai.msu.su/~megera/wiki/wildspeed) and pg_trgm of 9.1 (
http://www.postgresql.org/docs/9.1/static/pgtrgm.html).
--
With best regards,
Alexander Korotkov.
Small bugfix: in gistBufferingFindCorrectParent check that downlinkoffnum
doesn't exceed maximal offset number.
--
With best regards,
Alexander Korotkov.
gist_fast_build-0.14.3.patch.gz
Description: GNU Zip compressed data
--
Sent via pgsql-hackers mailing list (pgsql-hackers
).
I'm requesting real-life datasets which makes troubles in real life from
Oleg. Probably those datasets is even larger or new linear split produce
less overlaps on them.
--
With best regards,
Alexander Korotkov.
| cartwheel's
28453 | cartwheeling
28455 | carve
28457 | carver
28459 | carvers
28461 | carving
28463 | carvings
(23 rows)
--
With best regards,
Alexander Korotkov.
regards,
Alexander Korotkov.
(1,1000));
--
With best regards,
Alexander Korotkov.
On Tue, Aug 30, 2011 at 9:29 PM, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
On 30.08.2011 13:29, Alexander Korotkov wrote:
On Tue, Aug 30, 2011 at 1:13 PM, Heikki Linnakangas
heikki.linnakangas@**enterprisedb.comheikki.linnakan...@enterprisedb.com
wrote:
So, over 50
which is attached as
'indexes.sql'. Also, similar script with different index names I'm running
with my split patch.
Feel free to ask questions about all this stuff.
--
With best regards,
Alexander Korotkov.
fastbuild_test.php.gz
Description: GNU Zip compressed data
plantuner.patch.gz
index with almost zero overlaps. But new
linear split produces huge overlaps in this case. That's why I decided to
make some experiments with another split algorithm.
--
With best regards,
Alexander Korotkov.
and while only 50% of index is complete (estimated by file sizes).
Also, automatic switching to buffering build shows better index quality
results in all the tests. While it's hard for me to explain that.
--
With best regards,
Alexander Korotkov.
On Wed, Aug 17, 2011 at 11:11 AM, Alexander Korotkov
aekorot...@gmail.comwrote:
On Tue, Aug 16, 2011 at 11:15 PM, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
On 16.08.2011 22:10, Heikki Linnakangas wrote:
Here's an version of the patch with a bunch of minor changes
on the right way. btree_gist is an extension which provides
GiST indexing of scalar datatype. UUID is one of them. So, the module you
are writing should be quite similar.
--
With best regards,
Alexander Korotkov.
to start rerunning the tests now.
--
With best regards,
Alexander Korotkov.
I found that I forgot to remove levelstep and buffersize from reloptions.c.
Updated patch is attached.
--
With best regards,
Alexander Korotkov.
gist_fast_build-0.14.1.patch.gz
Description: GNU Zip compressed data
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org
(maintenance_work_mem_in_pages - 1))
and get more precise result. But also we need at least very rough estimate
of memory occupied by node buffers hash tab and path items.
--
With best regards,
Alexander Korotkov.
tuples directly from the
heap.
Yes, seems reasonable. Buffer on the root node was in the paper. But now I
don't see the need of it too.
--
With best regards,
Alexander Korotkov.
Hi!
Thank you for your notes.
On Fri, Aug 12, 2011 at 7:04 PM, Robert Haas robertmh...@gmail.com wrote:
On Thu, Aug 11, 2011 at 6:21 AM, Alexander Korotkov
aekorot...@gmail.com wrote:
[ new patch ]
Some random comments:
- It appears that the noFollowFight flag is really supposed
explicitly, and
stop the emptying process only if one of the lower-level buffers really
fills up? That should be more efficient, as you would have swap between
different subtrees less often.
Yes, it seems reasonable to me.
--
With best regards,
Alexander Korotkov.
,
Alexander Korotkov.
to understand without some explanation.
Some comments were added. I'm working on more of them.
--
With best regards,
Alexander Korotkov.
gist_fast_build-0.13.0.patch.gz
Description: GNU Zip compressed data
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes
On Thu, Aug 11, 2011 at 2:28 PM, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
On 10.08.2011 22:44, Alexander Korotkov wrote:
Manual and readme updates.
Thanks, I'm reviewing these now.
Do we want to expose the level-step and buffersize parameters to users?
They've been
and
effective_cache_size.
4) Some renames. In particular GISTLoadedPartItem
to GISTBufferingInsertStack.
5) Some comments were corrected and some were added.
6) pgindent
7) rebased with head
Readme update and user documentation coming soon.
--
With best regards,
Alexander Korotkov.
gist_fast_build-0.11.0
Manual and readme updates.
--
With best regards,
Alexander Korotkov.
gist_fast_build-0.12.0.patch.gz
Description: GNU Zip compressed data
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql
reloption too, if we had that). Please start a new thread on that on
pgsql-hackers.
Ok.
--
With best regards,
Alexander Korotkov.
].default_val’**)
It is caused by definition of default field of relopt_string structure as
1-length character array. This seems to be a design flaw in the reloptions.c
code. Any thoughts?
--
With best regards,
Alexander Korotkov.
*default_val;
is possible?
--
With best regards,
Alexander Korotkov.
that both were added by your commit
of table-based parser:
http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=ba748f7a11ef884277b61d1708a17a44acfd1736
--
With best regards,
Alexander Korotkov.
large tree with levelstep = 1 size of this datastructures
will be singnificant. And it's hard to predict that size without knowing of
tree size.
--
With best regards,
Alexander Korotkov.
gist_fast_build-0.10.0.patch.gz
Description: GNU Zip compressed data
--
Sent via pgsql-hackers mailing
901 - 1000 of 1172 matches
Mail list logo
