Tag Info

New answers tagged

1

This was a bug in pgagent, it has been fixed in http://git.postgresql.org/gitweb/?p=pgagent.git;a=commitdiff;h=f9bf1ccb27ebcfce00e7a6d467bc0e1b5ee9555e.


1

Each pgAdmin query window has it's own session. You can run one transaction at a time in each session. It's not possible to run two transactions concurrently in the same session (at least not in pgAdmin or psql). You can open and bind more sessions to the same query window with the "connection bar" in the menu of the query window, then switch between ...


0

I've found it ! In Windows Service, i found that it was "adminpostgres" who was running the pgAgent service. I just had to edit the pgpass.conf in c:/user/adminpostgres/AppData/postgresql with my old config to make it works !


1

I talked to someone who helped me find the answer. The correct syntax is, for anyone in future reference. The documentation mentions it, although it can be easy to miss. START TRANSACTION; DROP SCHEMA IF EXISTS replays CASCADE; CREATE SCHEMA replays; CREATE ROLE admins WITH PASSWORD 'changeme'; GRANT SELECT ON ALL TABLES IN SCHEMA replays TO PUBLIC; ...



Top 50 recent answers are included