> > What's your time zone setting?
I'm baffled
I disconnected my psql-client, reconnected a while later to demonstrate this
problem to someone on the server I stop/started earlier, and the problem
wasn't there anymore. This is the one I stopped, set TZ and started
again. However, since
> What's your time zone setting?
> Also, are you using --enable-integer-datetimes?
I'm running Slack v8 (with some updates, but still), so TZ is not defined as
environment variable, but it's using 'Europe/Amsterdam'.
I've verified whether setting TZ made a difference (stop/starting the server),
On Thu, 21 Aug 2003, Tom Lane wrote:
> Stephan Szabo <[EMAIL PROTECTED]> writes:
> >>> This still doesn't explain why Arnold sees a failure with to_date and
> >>> we don't, though.
>
> > Wait, he's in australia, what if he's getting the edge case the other way.
> > It starts out on the 14th, does
"ir. F.T.M. van Vugt bc." <[EMAIL PROTECTED]> writes:
> Will you allow me to add to this wackyness with the following on CVS tip from
> this morning:
What's your time zone setting? Also, are you using
--enable-integer-datetimes?
regards, tom lane
Stephan Szabo <[EMAIL PROTECTED]> writes:
>>> This still doesn't explain why Arnold sees a failure with to_date and
>>> we don't, though.
> Wait, he's in australia, what if he's getting the edge case the other way.
> It starts out on the 14th, does the timezone conversion. But then it
> looks lik
hi
i need help urgently to understand how postgres
manages its connection pool , how it manages deadlock . we are using postgres
for our supply chain mgmt system and we are facding connectin related
problems..
plz cud u direct me to some relevant
resources/urls
regards
annu
To
The Respected sir,
I am umamahesh.I am trying to install postgresql in compaq tru64 unix.
i choose postgresql-7.3.3.
1) for this i choose make-3.80 from GNU.org site.is it work or not.
2) after installing make-3.80 i use the command make is this software is sufficent in place of gmake.
3) In
On Thu, 21 Aug 2003, Stephan Szabo wrote:
> On Thu, 21 Aug 2003, Stephan Szabo wrote:
>
> > On Thu, 21 Aug 2003, Tom Lane wrote:
> >
> > > Stephan Szabo <[EMAIL PROTECTED]> writes:
> > > > Hmm, I just got my machine to give a similar failure mode with
> > > > a slightly wacky input.
> > >
> > > P
Giacomo Cariello <[EMAIL PROTECTED]> writes:
> void repalloc_bubble(u_int8_t *buf, u_int32_t s)
> {
> buf = repalloc(buf, s);
> bzero(buf, s);
> }
> repalloc_bubble(d->buf, d->size);
This doesn't update d->buf in the calling function; the result of
repalloc is only assi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
PostgreSQL 7.3.2 (Redhat 9)
When creating a table, primary key indexes and serial sequences are created
as well. Naively altering the name of the table does not modify the names
of the dependent primary key indexes and serial sequences. It was expec
> > > Hmm, I just got my machine to give a similar failure mode with
> > > a slightly wacky input.
Will you allow me to add to this wackyness with the following on CVS tip from
this morning:
free4testing=# select version();
version
---
On Thu, 21 Aug 2003, Stephan Szabo wrote:
> On Thu, 21 Aug 2003, Tom Lane wrote:
>
> > Stephan Szabo <[EMAIL PROTECTED]> writes:
> > > Hmm, I just got my machine to give a similar failure mode with
> > > a slightly wacky input.
> >
> > Perhaps more to the point:
> >
> > regression=# select timest
On Thu, 21 Aug 2003, Tom Lane wrote:
> Stephan Szabo <[EMAIL PROTECTED]> writes:
> > Hmm, I just got my machine to give a similar failure mode with
> > a slightly wacky input.
>
> Perhaps more to the point:
>
> regression=# select timestamptz '1901/12/13 0:0:0';
> timestamptz
> --
Boris Folgmann <[EMAIL PROTECTED]> writes:
> Look closely: postmaster now thinks that the first argument 1.0 is NUMERIC,
Yup. This is not a bug, it's intentional (and per SQL spec, AFAICT).
Your problem is that 123::real/25 yields a double precision result,
which is not implicitly castable to re
Stephan Szabo <[EMAIL PROTECTED]> writes:
> Hmm, I just got my machine to give a similar failure mode with
> a slightly wacky input.
Perhaps more to the point:
regression=# select timestamptz '1901/12/13 0:0:0';
timestamptz
-
1901-12-13 00:00:00
(1 row)
regression=# sel
Hi!
I've triggered a type related problem in postgresql-7.3.2-3
It worked in postgresql-7.2.3-5.80.
CREATE OR REPLACE FUNCTION _rmin(REAL, REAL)
RETURNS REAL AS '
BEGIN
IF $1 <= $2 THEN
RETURN $1;
ELSE
RETURN $2;
END IF;
END;
' LANGUAGE 'plp
Giacomo Cariello <[EMAIL PROTECTED]> writes:
> Using repalloc in some functions in a shared library I load, the effect is
> not the desidered one: the allocated area gets overwritten and causes
> segfault once the function returns or calls SPI_finish()
The odds that this is a bug in repalloc, an
17 matches
Mail list logo
