On 19/05/2019 22:37, John Fawcett via dovecot wrote:

On 19/05/2019 20:31, mabi via dovecot wrote:

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

On Sunday, May 19, 2019 7:36 PM, John Fawcett via dovecot <dovecot@dovecot.org> wrote:

Attached is a tentative patch. I've verified no regression for mysql. There should be no regression for sqlite as the code path is identical.

Are you able to test for pgsql? As mentioned by Akie it will break for PostgresSql < 9.5 but probably it was not working anyway due to duplicate keys. Whether this is a wider problem depends on whether the insert code is being used for other purposes too.

If you or someone can verify it works on PostgresSql >= 9.5, then the next step will be to make it conditional on the version.

Thank you very much John for your patch, that's fantastic. I am on OpenBSD 6.5 and will recompile dovecot from the ports by adding your patch to it, I hope that works and will let you know if I managed. If I understand correctly the relevant binary file I need to replace is the following right:

/usr/local/lib/dovecot/dict/libdriver_pgsql.so

or are there any others I also need to replace in order to test? I am planning to test live by just replacing the relevant file(s) so that I hopefully don't need to re-install the whole dovecot package.

I'm not sure how the source compilation works on OpenBSD, when I do it on linux and run "make install" it installs all relevant binaries/libraries.

I saw one issue with the fix though, it does not correctly pull out the username field. I'm wondering if the query can be rewritten not to mention the name of the field that fails the constraint....

John

so basically if this works just as well:

INSERT INTO last_logins (last_login,username,domain) VALUES (1558273000,'user@domain.tld','domain.tld') ON CONFLICT DO UPDATE SET last_login=1558273000,domain='domain.tld';

then the fix can be altered to attached file which is more similar to the MYSQL syntax and does not require extra logic to get the username field.

John

So looking into this with a postgresql databse to work with: the above query does not work. You have to specify either the column name or the constraint name that you expect to be violated in order for the update to take place.

With a map like this one you're using

map {
    pattern = shared/last-login/$user/$domain
    table = last_login
    value_field = last_login
    value_type = uint

    fields {
        username = $user
        domain = $domain
    }
}

there's no field name that is obviously the primary key. I've reworked the patch to use the postgres default primary key constraint name (tablename_pkey).

The attached fix should work in that case, although I feel it's not general enough.

John