Re: [GENERAL] Caching and Blobs in PG? Was: Can PG replace redis, amqp, s3 in the future?

2017-05-04 Thread Sven R. Kunze
On 03.05.2017 12:57, Thomas Güttler wrote: Am 02.05.2017 um 05:43 schrieb Jeff Janes: On Sun, Apr 30, 2017 at 4:37 AM, Thomas Güttler > wrote: Is is possible that PostgreSQL will replace these building blocks in the

Re: [GENERAL] Can PG replace redis, amqp, s3 in the future?

2017-05-01 Thread Sven R. Kunze
On 30.04.2017 16:25, Steve Atkins wrote: You can use postgresql for caching, but caches don't require the data durability that a database offers, and can be implemented much more efficiently. I for one can understand Thomas' need for a single solution. Just recently I needed a cache which was

Re: [GENERAL] Querying JSON Lists

2017-03-03 Thread Sven R. Kunze
On 03.03.2017 16:05, Adrian Klaver wrote: https://www.postgresql.org/docs/9.6/static/functions-json.html As to why it works on JSON arrays: Table 9-43. Additional jsonb Operators " ? text Does the string exist as a top-level key within the JSON value? " So to be picky it not does

Re: [GENERAL] ERROR: functions in index expression must be marked IMMUTABLE

2017-03-03 Thread Sven R. Kunze
On 03.03.2017 11:43, Geoff Winkless wrote: ​One alternative would be to make to_date accept all language variants of months simultaneously. A quick search of google suggests that there aren't any overlaps between languages (ie where one language uses "Foo" for March and another uses "Foo" for

Re: [GENERAL] ERROR: functions in index expression must be marked IMMUTABLE

2017-03-03 Thread Sven R. Kunze
On 03.03.2017 11:43, Geoff Winkless wrote: One alternative would be to make to_date accept all language variants of months simultaneously. A quick search of google suggests that there aren't any overlaps between languages (ie where one language uses "Foo" for March and another uses "Foo" for

Re: [GENERAL] DISTINCT vs GROUP BY - was Re: is (not) distinct from

2017-03-03 Thread Sven R. Kunze
On 03.03.2017 06:26, George Neuner wrote: I know most people here don't pay much - or any - attention to SQLServer, however there was an interesting article recently regarding significant performance differences between DISTINCT and GROUP BY as used to remove duplicates.

Re: [GENERAL] Querying JSON Lists

2017-03-03 Thread Sven R. Kunze
On 28.02.2017 17:33, Adrian Klaver wrote: On 02/26/2017 03:26 AM, Sven R. Kunze wrote: Hello everyone, playing around with jsonb and coming from this SO question http://stackoverflow.com/questions/19925641/check-if-a-postgres-json-array-contains-a-string I wonder why PostgreSQL behaves

Re: [GENERAL] ERROR: functions in index expression must be marked IMMUTABLE

2017-03-01 Thread Sven R. Kunze
On 01.03.2017 14:40, Geoff Winkless wrote: On 1 March 2017 at 13:36, Sven R. Kunze <srku...@mail.de <mailto:srku...@mail.de>>wrote: On 28.02.2017 17:50, David G. Johnston wrote: Supposedly one could provide a version of to_date that accepts a locale in which to int

Re: [GENERAL] ERROR: functions in index expression must be marked IMMUTABLE

2017-03-01 Thread Sven R. Kunze
On 28.02.2017 17:50, David G. Johnston wrote: ​That would seem to be it. cache_locale_time() at the top of DCH_to_char which is in the call stack of the shared parsing code for both to_date and to_timestamp.

Re: [GENERAL] ERROR: functions in index expression must be marked IMMUTABLE

2017-02-28 Thread Sven R. Kunze
On 28.02.2017 15:40, Adrian Klaver wrote: [explanation of why date casting and to_datetime don't work] Why is to_date not immutable? Regards, Sven -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription:

Re: [GENERAL] ERROR: functions in index expression must be marked IMMUTABLE

2017-02-28 Thread Sven R. Kunze
On 27.02.2017 18:17, Adrian Klaver wrote: Yes, but is not about timezone dependency, it is about the other dependencies listed in the second and third points. Namely the datestyle setting and magic strings e.g. 'now' I am sorry, I still don't understand. to_date and to_timestamp require

Re: [GENERAL] ERROR: functions in index expression must be marked IMMUTABLE

2017-02-27 Thread Sven R. Kunze
On 27.02.2017 16:37, Adrian Klaver wrote: On 02/27/2017 07:03 AM, Sven R. Kunze wrote: Why is this relevant for dates? I cannot see that dates are timezone-influenced. Per Tom's post, see points 2 & 3: Maybe, I am on a completely wrong track here, but to me dates still don't look time

Re: [GENERAL] ERROR: functions in index expression must be marked IMMUTABLE

2017-02-27 Thread Sven R. Kunze
On 27.02.2017 12:10, Geoff Winkless wrote: On 27 February 2017 at 10:52, Sven R. Kunze <srku...@mail.de <mailto:srku...@mail.de>>wrote: So, what can I do to parse texts to date(times) in a safe manner? You know best the format of your data; if you know that your date fie

Re: [GENERAL] ERROR: functions in index expression must be marked IMMUTABLE

2017-02-27 Thread Sven R. Kunze
Hi Geoff, Adrian and Tom, thanks for your responses so far. Excuse my late response. I will respond to Tom's mail as it covers most points: On 26.02.2017 17:50, Tom Lane wrote: There are multiple reasons why the text-to-datetime conversion functions are not immutable: * some of them depend

[GENERAL] Querying JSON Lists

2017-02-26 Thread Sven R. Kunze
Hello everyone, playing around with jsonb and coming from this SO question http://stackoverflow.com/questions/19925641/check-if-a-postgres-json-array-contains-a-string I wonder why PostgreSQL behaves differently for text and integers on the ? and @> operators. Let's have a look at 4

[GENERAL] ERROR: functions in index expression must be marked IMMUTABLE

2017-02-26 Thread Sven R. Kunze
Hello everybody, I'd like to implement a btree date index from json input data. >>># \d docs Table "public.docs" Column | Type | Modifiers +-+--- id | integer | not null default

Re: [GENERAL] [to_tsvector] German Compound Words

2015-06-01 Thread Sven R. Kunze
, 2015 at 6:34 PM, Sven R. Kunze srku...@tbz-pariv.de mailto:srku...@tbz-pariv.de wrote: Sure. Here you are: =# select ts_debug('public.german_compound', 'wasserkraft'); ts_debug

Re: [GENERAL] [to_tsvector] German Compound Words

2015-06-01 Thread Sven R. Kunze
} | german_ispell | {datenbank,daten,date,banken,daten,date,bank,daten,date,banken,daten,date,bank} On 01.06.2015 09:25, Sven R. Kunze wrote: I actually wanted to minimize the installation effort. Thus, I used the hunspell-de-de package of Debian/Ubuntu. Give me a second for ispell. Below, see

[GENERAL] [to_tsvector] German Compound Words

2015-05-28 Thread Sven R. Kunze
. What have I done wrong here? -- Sven R. Kunze TBZ-PARIV GmbH, Bernsdorfer Str. 210-212, 09126 Chemnitz Tel: +49 (0)371 33714721, Fax: +49 (0)371 5347920 e-mail: srku...@tbz-pariv.de web: www.tbz-pariv.de Geschäftsführer: Dr. Reiner Wohlgemuth Sitz der Gesellschaft: Chemnitz Registergericht

Re: [GENERAL] [to_tsvector] German Compound Words

2015-05-28 Thread Sven R. Kunze
for the compound words such as: wasserkraft - wasserkraft, kraft schifffahrt - schifffahrt, fahrt blindflansch - blindflansch, flansch etc. What have I done wrong here? -- Sven R. Kunze TBZ-PARIV GmbH, Bernsdorfer Str. 210-212, 09126 Chemnitz Tel: +49 (0)371 33714721

[GENERAL] [plainto_tsquery] using OR

2015-05-27 Thread Sven R. Kunze
features of tsquery that PostgreSQL could provide from the user. Is there a way to safely create a tsquery out of user's input? Optionally, when the user types '', '|', '!' '(' and ')' it could be interpreted like typical tsquery syntax BUT still creates valid tsquery. Regards, -- Sven R

[GENERAL] [tsvector] to_tsvector called multiple times

2015-05-26 Thread Sven R. Kunze
to it as well. The interesting problem here is that PostgreSQL maps the stem itself ('system') to a completely different stem ('syst'). Should a stem not remain stable even when to_tsvector is called on it multiple times? -- Sven R. Kunze TBZ-PARIV GmbH, Bernsdorfer Str. 210-212, 09126 Chemnitz Tel

Re: [GENERAL] [tsvector] to_tsvector called multiple times

2015-05-26 Thread Sven R. Kunze
: Sven R. Kunze wrote: However, are you sure, I am using snowball? Maybe, I am reading the documenation wrong: test= SELECT * FROM ts_debug('german', 'system'); alias | description | token | dictionaries | dictionary | lexemes

Re: [GENERAL] [tsvector] to_tsvector called multiple times

2015-05-26 Thread Sven R. Kunze
For future reference: https://github.com/snowballstem/snowball/issues/19 On 26.05.2015 12:29, Sven R. Kunze wrote: Thanks. It seems as if I have use snowball. So, I go ahead and post my issue at github. Maybe, I have difficulties to understand the relationship/dependencies between all

Re: [GENERAL] [tsvector] to_tsvector called multiple times

2015-05-26 Thread Sven R. Kunze
, you can have small personal dictionary (before stemmer) with such exceptions, for example, use synonym template system system Oleg On Tue, May 26, 2015 at 11:18 AM, Sven R. Kunze srku...@tbz-pariv.de mailto:srku...@tbz-pariv.de wrote: Hi everybody, the following stemming results

Re: [GENERAL] [tsvector] to_tsvector called multiple times

2015-05-26 Thread Sven R. Kunze
Thanks Albe for that detailed answer. On 26.05.2015 11:01, Albe Laurenz wrote: Sven R. Kunze wrote: the following stemming results made me curious: select to_tsvector('german', 'systeme'); 'system':1 select to_tsvector('german', 'systemes'); 'system':1 select to_tsvector('german', 'systems

Re: [GENERAL] [tsvector] to_tsvector called multiple times

2015-05-26 Thread Sven R. Kunze
I think I understand now. Thus, the issue at hand could (maybe) be solved by passing words first to one of those more elaborate dictionaries (myspell, hunspell or ispell) and if still necessary then to snowball. Did I get this right? On 26.05.2015 13:38, Albe Laurenz wrote: Sven R. Kunze