>> ALTER SEQUENCE ... OWNER TO ...;
>> GRANT ... ON SEQUENCE ... TO ...;
>> ...
>>
>
>I don't quite understand why it should be your way and not the other. Care
>to
>explain?
>
>Regards.
>
>
>--
>Guillaume.
Oops, sorry, there is no syntax ALTER SEQUENCE ... OWNER TO ...;
But since release 8.2,
For sequences, the DDL script generated looks like:
CREATE SEQUENCE ...;
ALTER TABLE ... OWNER TO ...;
GRANT ... ON TABLE ... TO ...;
...
... but should be:
...
ALTER SEQUENCE ... OWNER TO ...;
GRANT ... ON SEQUENCE ... TO ...;
...
Regards,
Dmitry.
--
Sent via pgadmin-support mailing list
When a new function is created, the initial default EXECUTE privilege is
granted to PUBLIC (this is described is the documentation), and pgAdmin
generates the followng script:
CREATE OR REPLACE FUNCTION ... ;
ALTER FUNCTION ... OWNER TO ...;
The function's ACL is dispayed in the 'ACL' field in
When any server configuration parameters (or variables) are set on a
per-function basis, the script displayed in the pgAdmin SQL pane looks like
this:
CREATE OR REPLACE FUNCTION ... ;
ALTER FUNCTION ... SET ...;
If then I edit the function body and save my work, all variables are lost,
since (
>> Generally, it's perfectly clear that we can get job execution delay up to
>> the poll interval time. A proposed improvement for the pgAgent that might
>> be
>> taken into account in the future is to store last read schedules
>> (relative
>> to the server's real time) locally. And then to conne
> Nope, no changes.
Really it seems there are :)) Exploring the embedded manifests in the both
executables I found an additional dependency in the new one:
It relates to the Security update for Microsoft Visual C++ 2005 Service Pack
1 Redistributable Package:
http://support.mi
> Yes, but maybe you don't have the right runtimes installed on your
> machine. Does the original build work on that box? Where did you get
> that from?
Here is some additional info, which may help to localize the problem. What
reports the message "The system cannot execute the specified program"
>> I tried this new binary, and upon start both Windows XP and Server 2003
>> report "The system cannot execute the specified program". Is it built for
>> Windows?
>
> Yes, but maybe you don't have the right runtimes installed on your
> machine. Does the original build work on that box? Where did y
> I'll assume you've realised that setting the poll time to 600 means
> that jobs will run up to 10 minutes late?
>
> Regardless of that, you are correct that this behaviour is
> undesirable. Please try the replacement binary at
> http://uploads.enterprisedb.com/download.php?file=624b234667456b2208
Hello,
The first time I tried to setup the pgAgent job scheduler on Windows I was
wondered the service couldn't start for a very long time. Further
investigation shown that the 'poll time interval' executable parameter (-t)
affects startup time. Moreover, startup time directly reflects this
parame
10 matches
Mail list logo
