> I get the right answer from current sources, and the wrong one on 7.0.2.
> It's ye olde date-to-timestamp-off-an-hour-at-DST-boundary problem.
> Are you not running in a USA timezone?
Oh right. I'm usually in GMT, which is a bad place to test time zone
behavior, eh?
- Tho
Thomas Lockhart <[EMAIL PROTECTED]> writes:
>> Query to reproduce the bug (7.0.3):
>> edge=# select date_part('dow','4/1/2001'::date)::int4;
>> --
>> 6
> I'm not seeing this on my 7.0.2 RPM installation, or on my from-cvs
> current sources (dow for April 1 comes up as zero, as you would e
Version: cvs checkout -r REL7_1_BETA3 pgsql
Platform: RedHat 6.2
Running the regression test:
./pg_regress --schedule=/path/src/test/regress/parallel_schedule
--port=65432 --multibyte= numeric_big
I encountered the following regression error. Rerunning the regression went
fine. Given this is t
http://www.postgresql.org/bugs/index.php indicates that the address
[EMAIL PROTECTED] exists. It does not. ;-)
The original message was received at Wed, 17 Jan 2001 19:00:28 -0500 (EST)
from [209.43.202.2]
- The following addresses had permanent fatal errors -
<[EMAIL PROTECTED]>
I believe this is fixed in 7.1beta.
[ Charset KOI8-R unsupported, converting... ]
>
> POSTGRESQL BUG REPORT TEMPLATE
>
OK, I can confirm that this is fixed in 7.0.
[ Charset ISO-8859-1 unsupported, converting... ]
> The only problem with this is that we have a product in
> the field using 6.x. We plan to move to 7 at some point
> but that requires some planning, and major development
> efforts, since more than o
kevin koch (kevin.koch@compaq,.com) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
install/regression test instructions don't work.
Long Description
When following the V7.0.3 regression test instructions after building on my Alpha
Linux box, get
Alexander Klimov <[EMAIL PROTECTED]> writes:
> Undefined first referenced
> symbol in file
> heap_sysoffset catalog/SUBSYS.o
Either you don't have an up-to-date set of source files, or you have
out-of-date object files. Do y
> Query to reproduce the bug (7.0.3):
> edge=# select date_part('dow','4/1/2001'::date)::int4;
> --
> 6
> Clearly, the first of April ... is not on Saturday ... (and my app) was displaying
>April
> 2001 wrong.
I'm not seeing this on my 7.0.2 RPM installation, or on my from-cvs
cu
[EMAIL PROTECTED] writes:
> edge=# select date_part('dow','4/1/2001'::date)::int4;
> ?column?
> --
> 6
> (1 row)
Seems to be fixed in current sources:
regression=# select date_part('dow','4/1/2001'::date)::int4;
?column?
--
0
(1 row)
I think this is a side-ef
Try the postmaster.init file.
(I would suggest, next time, try using the pgsql-general or pgsql-admin,
mailing list).
Good day.
Alfonso Peniche
Antonio Da Silva wrote:
To whom this may concernCan
you please tell me how to set the PGDATA environmental variable.The
problem is that I cannot find t
Query to reproduce the bug (7.0.3):
edge=# select date_part('dow','9/1/2001'::date)::int4;
?column?
--
6
(1 row)
edge=# select date_part('dow','4/1/2001'::date)::int4;
?column?
--
6
(1 row)
Clearly, the first of April and September are not both on the same
Hi.
I get psql from CVS and try
configure --with-tcl --with-perl --with-python --with-openssl --with-CXX
&& make
And I got
...
gcc -Wall -Wmissing-prototypes -Wmissing-declarations
-L/usr/local/ssl/lib -Wl,-R/usr/local/pgsql/lib access/SUBSYS.o
bootstrap/SUBSYS.o catalog/SUBSYS.o parser/SUBSYS.
I use a DIGITAL ALPHA DEC2000 AXP500 with 128MB of RAM, architecture EV4
150MHz processor. I installed a Debian potato (2.2) and got problems
during installation, postmaster not starting.
After a mail exchange with postgres Debian mantainer, got sources of
postgresql version 7.0.3 (debian patched)
To whom this may concern
Can you please tell me how to set the PGDATA environmental
variable.
The problem is that I cannot find this variable.
Thanking you in advance
Antonio
"José Antonio Matute Calvo" wrote:
>
> Problem:
> If try to use field of type "java.sql.Types.BIT" obtains error "Unknown
> Types Value"
>
> Resolution:
>
> Add this:
>
> PreparedStatement.java
> 460,461d459
> < case Types.BIT:
> <
Ing. Pavel Janousek ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
ECPG, cursors and transactions
Long Description
When I use ECPG in transactions I got some bad results - I think that this results are
bug, but I'm not sure..
Ing. Pavel Janousek ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
Bad rights working in referential integrity?
Long Description
I have two tables:
create table a(id serial primary key, t text);
create table b(id int reference
18 matches
Mail list logo