Hi,
I am attempting to get a plpgsql function to work (the function is
listed below and the server is psql 7.2.3) and I keep getting
alternating errors. When called once the error seen is:
NOTICE: Error occurred while executing PL/pgSQL function
ordcred_internal
NOTICE: Parser: pa
Jeffery Read <[EMAIL PROTECTED]> writes:
> I am attempting to get a plpgsql function to work (the function is
> listed below and the server is psql 7.2.3) and I keep getting
> alternating errors.
I think you're hitting 7.2 bugs. If you can reproduce the misbehavior
in 7.3.4 then I'd be inte
I am not sure but i thought I read something of this
problem and maybe its not a problem but my
understanding.
There are only 30 days in september however I can not
seem to make a query that asks for october 1.
proofduedate is time stamp with zone
maybe this is the problem but I am a little los
On Wed, Oct 01, 2003 at 10:26:57 -0700,
Theodore Petrosky <[EMAIL PROTECTED]> wrote:
> I am not sure but i thought I read something of this
> problem and maybe its not a problem but my
> understanding.
>
> There are only 30 days in september however I can not
> seem to make a query that asks for
pg_dump version: 7.3.4
pg_restore version: 7.3.4
psql version: 7.3.4
I try to use the various scenarios proposed in the pg_dump man page to dump
one database and restore it on another machine. In all case, I have got an
error during the restore process (psql -d xxx -f yyy or pg_restore).
I have c
Hi,
I hit the following bug:
this is with a 7.3.4 database server (and psql client)
PGCLIENTENCODING="UTF-8"
and a utf-8 encoded database,
pensieve=> create table a(raw bytea);
CREATE TABLE
pensieve=> insert into a values('\770\711\056'::bytea);
INSERT 1112630 1
pensieve=> vacuum analyze a;
VACU
Michael Radziej <[EMAIL PROTECTED]> writes:
> I think bytea should accept ANY value and vaccuum analyze must
> not complain about this.
This is fixed as of 7.4, I think (at least your example case doesn't
fail for me). 7.3 was a bit sloppy about how it treated entries in
pg_statistic ...
I am sorry, I wasn't clear... when i refered to
01 October 2003
I got zero results. I only got results for the October
1 date when i refered to it as september 31
I am on 7.3.4 on OS X
Ted
--- Bruno Wolff III <[EMAIL PROTECTED]> wrote:
> On Wed, Oct 01, 2003 at 10:26:57 -0700,
> Theodor
Theodore Petrosky <[EMAIL PROTECTED]> writes:
> I am sorry, I wasn't clear... when i refered to
> 01 October 2003
> I got zero results. I only got results for the October
> 1 date when i refered to it as september 31
That's a bit hard to believe. Could you show us the results of the
individu
here is the actual query:
agencysacks=# SELECT jobnumseq, (SELECT cname FROM
clientinfo ci WHERE ci.acode = j.clientid) as client,
shrtdesc, to_char(proofduedate, 'Dy FMMon DD,
HH12 am') FROM jobs j WHERE proofduedate BETWEEN
to_timestamp('01 October 2003 00:01', 'DD Month
HH24:MI')
I should have sent this... it is very interesting..
agencysacks=# select to_timestamp('01 October 2003
00:01', 'DD Month HH24:MI');
to_timestamp
-
0003-10-01 00:01:00
(1 row)
agencysacks=# select to_timestamp('01 October 2003
23:59', 'DD Month HH24:MI');
I like this one:
agencysacks=# select to_timestamp('31 September 2003
23:59', 'DD Month HH24:MI');
to_timestamp
2003-10-01 23:59:00-04
(1 row)
agencysacks=# select to_timestamp('32 September 2003
23:59', 'DD Month HH24:MI');
to_timestamp
Theodore Petrosky <[EMAIL PROTECTED]> writes:
> I should have sent this... it is very interesting..
> agencysacks=# select to_timestamp('01 October 2003
> 00:01', 'DD Month HH24:MI');
> to_timestamp
> -
> 0003-10-01 00:01:00
> (1 row)
Oh ... duh ... you should ha
Simplest case to test is:
pg_ctl start -D /valid/db/dir -l /invalid/dir
pg_ctl: /invalid/dir: No such file or directory
postmaster successfully started
Postmaster hasn't started and the error could probably use some work.
Perhaps some more tests after line 340 of pg_ctl would be appr
Arguile <[EMAIL PROTECTED]> writes:
> Simplest case to test is:
> pg_ctl start -D /valid/db/dir -l /invalid/dir
> pg_ctl: /invalid/dir: No such file or directory
> postmaster successfully started
> Postmaster hasn't started and the error could probably use some work.
If you don't spec
On Thu, 2003-10-02 at 00:54, Tom Lane wrote:
> Arguile <[EMAIL PROTECTED]> writes:
> > Simplest case to test is:
> > pg_ctl start -D /valid/db/dir -l /invalid/dir
> > pg_ctl: /invalid/dir: No such file or directory
> > postmaster successfully started
>
> > Postmaster hasn't started and
16 matches
Mail list logo
