On Thu, Oct 19, 2017 at 04:54:19PM -0700, Igal @ Lucee.org wrote:
>
> My query at the moment is:
>
> SELECT name, popularity
> FROM temp.items3_v
> ,(values ('some phrase'::text)) consts(input)
> WHERE true
> and word_similarity(input, name) > 0.01 -- be lenient
Seems that would be easier and less error prone. Thanks,
--
Sent from: http://www.postgresql-archive.org/PostgreSQL-general-f1843780.html
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-gener
On Sat, Oct 21, 2017 at 8:24 AM, doganmeh wrote:
> Seems that would be easier and less error prone. Thanks,
>
>
>
> --
> Sent from: http://www.postgresql-archive.org/PostgreSQL-general-
> f1843780.html
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
> To make changes
On 2017-10-20 16:38, Tom Lane wrote:
Israel Brewster writes:
Can you send "explain" (not explain analyze) for the production
server?
Not for the full query - it only just completed, after 70 minutes or
so, and I wasn't running under EXPLAIN ANALYZE. Running with a shorter
date range of only
Thanks to everyone for your great answers
I have looked into pg_cron, jpgAgent and pgAutomator and enjoyed (j)pgAgent +
pgAdmin so far
pg_cron looks great but rewrite my 346 jobs seems painful
Adam your tool is really nice and I would be glad to help on this project, btw
I am not a developer b
Happy to hear jpgAgent is working alright for you. If you have any
questions with it feel free to ask me.
If you do want to help with pgAutomator, that sounds like something
you could start to learn on. jpgAgent is pretty much feature complete
as far as my needs go, and no one has requested any
The list approach for partial restore is also useful, thank you.
On another note, I used to take full backups (entire database), however
switched to table by table scheme in order to make it more VCS friendly.
Namely, so I only check into github the dumps of the tables that are updated
only.
S
On Sat, Oct 21, 2017 at 4:48 PM, doganmeh wrote:
> The list approach for partial restore is also useful, thank you.
>
> On another note, I used to take full backups (entire database), however
> switched to table by table scheme in order to make it more VCS friendly.
> Namely, so I only check into
On 10/21/2017 5:01 AM, Arthur Zakirov wrote:
PostgreSQL doesn't use index scan with functions within WHERE clause. So
you always need to use operators instead. You can try <% operator and
pg_trgm.word_similarity_threshold variable:
=# SET pg_trgm.word_similarity_threshold TO 0.1;
=# SELECT name,
