Hi,
Thank you for the review.
I fixed a typo and some comments. Please find new version attached.
---
Best regards,
Parfenov Aleksandr
On Fri, 19 Oct 2018 at 16:40, Anthony Bykov wrote:
> The following review has been posted through the commitfest application:
> make installcheck-world: teste
or we can change its behavior in this
way?
--
Aleksandr Parfenov
Postgres Professional: http://www.postgrespro.com
Russian Postgres Company
changes in some part (e.g. change of
enum without change of array). On the other hand, array content created
without array creation itself in .h file. Can we move actual array
creation into same .h file? What is the point to separate array content
definition and array definition?
--
Aleksandr Pa
re risking evaluating it more times than
>before.
>
> regards, tom lane
I reworked the patch and implemented processing of FuncScan in
pull_up_subqueries() in a way similar to VALUES processing. In order to
prevent folding of non-foldable functions it checks pr
On Tue, 28 Aug 2018 12:40:32 +0700
Aleksandr Parfenov wrote:
>On Fri, 24 Aug 2018 18:50:38 +0300
>Alexander Korotkov wrote:
>>Agreed, backward compatibility is important here. Probably we should
>>leave old dictionaries for that. But I just meant that if we
>>intro
oach will solve ambiguity in case of 'simple'
dictionary. Currently, it filters stop-words for the language, which
was selected during DB initialization.
--
Aleksandr Parfenov
Postgres Professional: http://www.postgrespro.com
Russian Postgres Company
Hello hackers,
Updated version of the patch in the attachment.
--
Aleksandr Parfenov
Postgres Professional: http://www.postgrespro.com
Russian Postgres Company
diff --git a/doc/src/sgml/textsearch.sgml b/doc/src/sgml/textsearch.sgml
index 8075ea94e7..a661373d1b 100644
--- a/doc/src/sgml
r.
I'm not an expert in PostgreSQL user-defined types, but AFAIK, it
doesn't require changes in PostgreSQL core, since types can be created
in extensions. It doesn't require changes to grammar or something.
You can look at citext contrib as an example.
--
Aleksan
y_tsvector @@ '''tupl'' & ''header'' &
''overhead'''::tsquery)
-> Bitmap Index Scan on message_body_idx (cost=0.00..224.16
rows=3 width=0)
Index Cond: (body_tsvector @@ '''tupl'&#
any suggestions/notices/critics about the idea and approach.
--
Aleksandr Parfenov
Postgres Professional: http://www.postgrespro.com
Russian Postgres Company
es
(cost=0.00..295752.80 rows=1 width=275)
Filter: (body_tsvector @@
to_tsquery('tuple&header&overhead'::text))
-> Function Scan on to_tsquery q (cost=0.25..0.26
rows=1 width=0)
(7 rows)
--
Aleksandr Parfenov
Postgres Professional: http
27;::tsquery
Negative distance support introduced to use it for AROUND operator
mentioned in websearch_to_tsquery[1]. In web search query language
AROUND(N) does a search for words within given distance N in
both forward and backward direction and it can be represented as <-N,N>
split some words using an arbitrary set of rules,
for instance "split all words containing digits". I propose merging
this patch provided that there are no objections.
I'm agree that this problem should be solved in separate patch and
that this feature can be merged without waiting for
words as one by using the special parser (as it done for hyphenated
word).
But in the example with websearch_to_tsquery, I think it should use
the same operator for quoted part of the query. For example, we can
update the operator in makepol before sending it to pushval
(pushval_morph) to do so.
It loo
he name of enum ts_parsestate looks more like a name of the function
than a name of a type.
In my version, it renamed to QueryParserState, but you can fix it if I'm
wrong.
--
Aleksandr Parfenov
Postgres Professional: http://www.postgrespro.com
Russian Postgres Companydiff --git a/src/
perator check in function TS_phrase_execute in
branches for negated operands.
--
Aleksandr Parfenov
Postgres Professional: http://www.postgrespro.com
Russian Postgres Company
The following review has been posted through the commitfest application:
make installcheck-world: tested, passed
Implements feature: tested, passed
Spec compliant: tested, passed
Documentation:tested, passed
Hi,
All information is related to WIP-tuplesort-memcontext-f
On Tue, 26 Dec 2017 13:51:03 +0300
Arthur Zakirov wrote:
> On Mon, Dec 25, 2017 at 05:15:07PM +0300, Aleksandr Parfenov wrote:
>
> Is I understood users need to rewrite their configurations if they
> use unaccent dictionary, for example. It is not good I think. Users
> will be u
Hi Arthur,
Thank you for the review.
On Thu, 21 Dec 2017 17:46:42 +0300
Arthur Zakirov wrote:
> I noticed that there are typos in the documentation. And I think it
> is necessary to keep information about previous sintax. The syntax
> will be supported anyway. For example, information about TSL
19 matches
Mail list logo
