GROUP BY mt.id;
CREATE UNIQUE INDEX IF NOT EXISTS movie_things_id_idx ON movie_things USING
btree (id);
ALTER MATERIALIZED VIEW movie_things CLUSTER ON movie_things_id_idx, OWNER
TO test;
On 21 July 2017 at 17:25, Jordan Gigov wrote:
> This is on version 9.5, 9.6 and 10beta2. I could probabl
This is on version 9.5, 9.6 and 10beta2. I could probably make a
test-case over the weekend if I'm at home.
On 21 July 2017 at 17:03, Tom Lane wrote:
> Jordan Gigov writes:
>> When running pg_restore as the superuser it gives the following error
>> pg_restore: [archiv
So we have this database dump created using "pg_dump -Fc ourdb >
file.dump" that has a Materialized View that gets refreshed under
certain conditions by our Java web-app.
When running pg_restore as the superuser it gives the following error
pg_restore: [archiver (db)] Error while PROCESSING TOC:
p
Just about every web developer encounters scenarios where they need to let
the user sort the results by the column they choose and that leads to
dangers of possible SQL injection, but also the loss of prepared statement
caching and optimizations (at least under Java with JPA). I have tried
using nu
