...
> I don't really consider this a bug; at least, fixing it would imply not
> const-simplifying the result expressions of CASEs, which is a cure far
> worse than the disease IMHO. Does anyone think we *should* allow CASE
> to defeat const-simplification?
No. Constant-folding during parsing sho
> the problem is
> my postgresql compile with enable multi bytes = unicode and my default
> language is BIG5 encoding, in previous version of postgresql 7.1
> i can use unicode encoding to do my back-end encoding and client
> encoding set to BIG5, with this setting i can insert a chinese word cod
I have applied a patch based on Tom's suggestion that will disable
VACUUM in a function in 7.3.
---
Rod Taylor wrote:
> 7.2 crashes with the below function:
>
> CREATE OR REPLACE FUNCTION runMaintenance()
> RETURNS BOOL AS
=?iso-8859-1?Q?Gr=E9gory_B=E9cue?= wrote:
>
> Hi all,
>
> I use actually MySQL Database but i have see your database and
> i think, it was better than MySQL. But i have just a question.
> When i have tested PostGreSQL, i have try to modidy the name of
> a columm but i'snt possible !!! And i have
Thomas Lockhart <[EMAIL PROTECTED]> writes:
|> > > I don't think that our code checks explicitly for a "-1" return, since
|> > > the range is checked just before the call, but it would probably be a
|> > > good idea if it did
|> > As I noticd yesterday, glibc's mktime() has in the current snapsho
I have stupid problem after
installation
I can't access my postgres db after
installation, when asking me the login and the password, i set 'postgres'
(i'm on root) and leave password to blank : don't work !
I try my system log & pass, same problem ...
Is there some changes on default
Thomas Lockhart <[EMAIL PROTECTED]> writes:
|> > This is the bug report against glibc that prompted the change:
|> >
|http://bugs.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=default&pr=2738
|> > |> Ah, but this might explain why I've always seen on my Linux box a 1
|> > |> second
Title: ENC: Datatype time PostGreSql 7.2.1
I am brazilian and work with o database PostGreSql 7.1.3.
I am upgrade PostGreSql 7.1.3 to 7.2.1 and find some bugs insert dataype time .
Example :
Create table teste( hour time);
\d tes
Hi,
I am trying to use postgreysql.
I am getting the following errors while creating a new database at
given location.
The errors are as shown below.
createdb -D /home/naren/ramu Ramu
ERROR: Absolute paths are not allowed as database locations
cr
> > date/time storage problem: timestamp parsed incorrectly...
>
> > It looks like a bad parser or defaults for time values. The
> > example code below explains the problem best. I'm not sure why,
> > or where... but it took me about a day to track down (PostgreSQL
> > is never wrong!). If I in
the problem is
my postgresql compile with enable multi bytes = unicode and my default
language is BIG5 encoding, in previous version of postgresql 7.1
i can use unicode encoding to do my back-end encoding and client
encoding set to BIG5, with this setting i can insert a chinese word code
(0xf9d6)
Hi all,
I use actually MySQL Database but i have see your database and i think, it was better
than MySQL. But i have just a question. When i have tested PostGreSQL, i have try to
modidy the name of a columm but i'snt possible !!! And i have see this for several
elements !!! It's a bug ?
To : PostgreSQL Person incharge
>From : anGie
RE : Problem with database
Dear sir,
I'm an academy student that interested about database
environment. Recently, I was using Kondara MNU/Linux 2.2
and Postgresql-7.1.1. for my studies.
According to your guidline, I had startup the postmaster
s
Thanks for the quick response. I see that pg_dumpall outputs the global
objects (-g) to stdout and that it cannot be combined with the -F or -f for
this reason. I would still like to be able to do a full database backup,
including all databases with oids and blobs, from a generic shell script
t
Sean Chittenden wrote:
>>>The FreeBSD folk are absolutely adamant about having mktime() no
>>>compensate for deadzones between DST shifts and they insist that
>>>the application handle this. Someone's off looking at how other
>>>OS'es handle this, but this could be an arduous battle on that
>>
> >The FreeBSD folk are absolutely adamant about having mktime() no
> >compensate for deadzones between DST shifts and they insist that
> >the application handle this. Someone's off looking at how other
> >OS'es handle this, but this could be an arduous battle on that
> >front. <:~)
>
> Personal
Cuttign down the CC: list this time, apologies if I cut too much and
someone misses a copy of this
Sean Chittenden wrote:
>
>The FreeBSD folk are absolutely adamant about having mktime() no
>compensate for deadzones between DST shifts and they insist that the
>application handle this. Some
17 matches
Mail list logo
