> On Sat, Aug 1, 2009 at 20:30, Kevin Field
> wrote:
> >> > The event viewer says:
> >> >
> >> > The description for Event ID ( 0 ) in Source ( PostgreSQL )
> > > > cannot
> >> > be
> >> > found. The local computer
> On Fri, Jul 31, 2009 at 19:29, Kevin Field
> wrote:
> >> > %t LOG: received fast shutdown request
> >> > %t LOG: aborting any active transactions
> >> > %t LOG: autovacuum launcher shutting down
> >> > %t LOG: shutting
> > %t LOG: received fast shutdown request
> > %t LOG: aborting any active transactions
> > %t LOG: autovacuum launcher shutting down
> > %t LOG: shutting down
> > %t LOG: database system is shut down
> >
> > That's the entire file. Attempting to start the service,
> On Wed, Jul 29, 2009 at 19:52, Kevin Field
> wrote:
> > On Win2k3 Std SP2, the service won't start once I've applied the
> > patch. In the log, I get:
> >
> > %t LOG: CreateProcess call failed: A blocking operation was
> > interrupted by a call
> I put the old binary back and it works fine.
For the record, "fine" meaning I've never had the shared memory
problem.
Kev
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Win2k3 Std SP2, the service won't start once I've applied the
patch. In the log, I get:
%t LOG: CreateProcess call failed: A blocking operation was
interrupted by a call to WSACancelBlockingCall.
(error code 2)
%t LOG: could not fork autovacuum worker process: A blocking
operation
On May 29, 12:43 pm, Kevin Field wrote:
> On May 29, 11:48 am, Kevin Field wrote:
>
>
>
> > On May 29, 11:35 am, robertmh...@gmail.com (Robert Haas) wrote:
>
> > > On Fri, May 29, 2009 at 7:59 AM, Kevin Field
> > > wrote:
> > > > On May 2
On May 29, 1:04 pm, t...@sss.pgh.pa.us (Tom Lane) wrote:
> Kevin Field writes:
> > default:
> >elog(ERROR, "unrecognized raise option: %d",
> > opt->opt_type);
> > Should this be changed to:
> > default:
> >
On May 29, 11:48 am, Kevin Field wrote:
> On May 29, 11:35 am, robertmh...@gmail.com (Robert Haas) wrote:
>
>
>
> > On Fri, May 29, 2009 at 7:59 AM, Kevin Field
> > wrote:
> > > On May 28, 5:19 pm, da...@kineticode.com ("David E. Wheeler") wrote:
>
On May 29, 11:48 am, Kevin Field wrote:
> On May 29, 11:35 am, robertmh...@gmail.com (Robert Haas) wrote:
>
>
>
> > On Fri, May 29, 2009 at 7:59 AM, Kevin Field
> > wrote:
> > > On May 28, 5:19 pm, da...@kineticode.com ("David E. Wheeler") wrote:
>
On May 29, 11:35 am, robertmh...@gmail.com (Robert Haas) wrote:
> On Fri, May 29, 2009 at 7:59 AM, Kevin Field
> wrote:
> > On May 28, 5:19 pm, da...@kineticode.com ("David E. Wheeler") wrote:
> >> On May 28, 2009, at 12:53 PM, Kevin Field wrote:
>
> >>
On May 28, 5:19 pm, da...@kineticode.com ("David E. Wheeler") wrote:
> On May 28, 2009, at 12:53 PM, Kevin Field wrote:
>
> >> Can pgTap check for a regex instead if just a string?
>
> > That's the other option, if the pgTAP author is willing...if the
>
On May 28, 3:28 pm, and...@dunslane.net (Andrew Dunstan) wrote:
> Kevin Field wrote:
> > I use pgTAP to make sure my functions produce the correct errors using
> > throws_ok(). So when I get an error from a plpgsql function, it looks
> > like this:
>
> > ERROR: upp
On May 28, 3:22 pm, t...@sss.pgh.pa.us (Tom Lane) wrote:
> Kevin Field writes:
> > I use pgTAP to make sure my functions produce the correct errors using
> > throws_ok(). So when I get an error from a plpgsql function, it looks
> > like this:
> > ERROR: upper bound
I use pgTAP to make sure my functions produce the correct errors using
throws_ok(). So when I get an error from a plpgsql function, it looks
like this:
ERROR: upper bound of FOR loop cannot be null
CONTEXT: PL/pgSQL function "foo" line 35 at FOR with integer loop
variable
...which I can then t
On May 14, 2:22 pm, Kevin Field wrote:
>
> Something I ran into though when trying to extend this logic to rules:
> for some reason rule definitions are compiled with "create rule x as "
> in front of them, unlike views, which just have everything after the
> "
On May 14, 2:22 pm, Kevin Field wrote:
>
> Something I ran into though when trying to extend this logic to rules:
> for some reason rule definitions are compiled with "create rule x as "
> in front of them, unlike views, which just have everything after the
> "
On May 13, 5:37 pm, gsm...@gregsmith.com (Greg Smith) wrote:
> On Wed, 13 May 2009, Kevin Field wrote:
> > Or would the only way to do this be to actually create a view and then
> > call pg_get_viewdef() and then delete the view?
>
> Just make it a temporary view and then it d
On May 13, 12:52 pm, t...@sss.pgh.pa.us (Tom Lane) wrote:
> Kev writes:
> > ... I was surprised
> > to find that some of my views of the form:
> > select.from b left join a on a.id=b.id
> > ...were being translated to this:
> > SELECT..FROM (B LEFT JOIN a ON ((a.id = b.id)))
> > ..
On May 13, 12:41 pm, kevin.gritt...@wicourts.gov ("Kevin Grittner")
wrote:
> Kevin Field wrote:
> > One other thing I'm just curious about, "!=" gets replaced with
> > "<>"...how come? (Feels more VB-ish than C-ish, so I was surprised
&
On May 13, 11:31 am, Kev wrote:
> Hi,
>
> I have a script that automatically generates the SQL to create some
> views. I'd like it to check whether its generated SQL matches the SQL
> returned by "select definition from pg_views where...". I've guessed
> most of the rules just by looking at the
On Apr 16, 10:52 am, mito wrote:
> By table structure i mean table definition options.
...which includes columns, right?
Sorry, I don't think I can picture what you're trying to do.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
On Apr 16, 3:14 am, mito wrote:
> Hi,
>
> i have built an SQL interface using rule system which supports row
> versioning and i would like to test it against Postgres SQL specification.
>
> Is there something like test cases for postgres SQL interface?
>
> Or do you have any ideas how to build a g
On Apr 8, 11:26 am, dp...@pgadmin.org (Dave Page) wrote:
> Did you add
>
> shared_preload_libraries = '$libdir/plugins/plugin_debugger.dll'
>
> to postgresql.conf and restart the server per the README?
Oh my goodness. No. Thank you so much. It works fine now. I'll
have to add that to my upgrad
On Apr 8, 10:32 am, dp...@pgadmin.org (Dave Page) wrote:
> On Wed, Apr 8, 2009 at 2:48 PM, Kevin Field wrote:
> >> I'll see if I can get an updated build pushed out sometime today.
>
> > I finally got around to trying this out using the March 24th build,
> > an
> I'll see if I can get an updated build pushed out sometime today.
I finally got around to trying this out using the March 24th build,
and it has the same issue...
Kev
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgre
26 matches
Mail list logo
