The following bug has been logged online:
Bug reference: 3563
Logged by: Randolf Richardson
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.4
Operating system: NetBSD 4 (beta), NetBSD 3.1, NetWare 6.5
Description:DATESTYLE feature suggestion
Details:
After
The following bug has been logged online:
Bug reference: 3567
Logged by: sapna kapoor
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.9
Operating system: RHEL 5.0 AS
Description:invalid page header in block of relation
Details:
We have database of 300 t
Randolf Richardson wrote:
> After convincing clients and colleagues to switch from Oracle (and others)
> to PostgreSQL, an issue that comes up is the need to customize DATESTYLE.
> Because this isn't possible, the developers who were against the move to
> PostgreSQL make it political and recommen
Hi,
pgbench contrib module is doing segmentation fault on Solaris
when -d option is specified without -p option specified.
This is because the -d option dumps the connection information
and the default value of pgport variable is NULL which causes
segmentation fault on Solaris when NULL is passe
Heikki Linnakangas wrote:
Randolf Richardson wrote:
After convincing clients and colleagues to switch from Oracle (and others)
to PostgreSQL, an issue that comes up is the need to customize DATESTYLE.
Because this isn't possible, the developers who were against the move to
PostgreSQL make
"sapna kapoor" <[EMAIL PROTECTED]> writes:
> some tables are giving error :
> ERROR: invalid page header in block 32655 of relation "" while
> accessing.
> Some are giving
> ERROR: could not access status of transaction 1778384896
> DETAIL: could not open file "pg_clog/06A0": No such file
Russell Smith wrote:
> The issue is output, not input.
>
> SET datestyle='dmy';
> SELECT '03-03-2004'::date
>
> Will return '2007-03-03', not 03-03-2004 as is the set datestyle.
You are aware that DateStyle controls both input and output,
_separately_, yes?
--
Alvaro Herrera
Randolf Richardson wrote:
>>> I'm hoping that this suggestion will be an easy one to implement.
>> Probably wouldn't be too hard.
>
> That's great! I'm guessing that this is due to the work already
> done with the to_char() function.
Just to be clear, I don't have any plans to actually do
Randolf Richardson wrote:
> After convincing clients and colleagues to switch from Oracle (and others)
> to PostgreSQL, an issue that comes up is the need to customize DATESTYLE.
> Because this isn't possible, the developers who were against the move to
> PostgreSQL make it political and recommend
> Randolf Richardson wrote:
>
> > After convincing clients and colleagues to switch from Oracle (and others)
> > to PostgreSQL, an issue that comes up is the need to customize DATESTYLE.
> > Because this isn't possible, the developers who were against the move to
> > PostgreSQL make it political
On Aug 22, 2007, at 10:13 , Randolf Richardson wrote:
The datestyle I need is "-Mon-DD" so that reports can easily be
generated that show dates like 2007-Aug-22. For people reading the
output, there will be absolutely no confusion about what the date is.
Are you generating report
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Yea, it isn't too hard to do, especially for output; input might be
> harder. This is the first request we have ever gotten for this so it is
> doubtful we would add this feature unless there is more demand.
I don't think any input-side changes are bei
The following bug has been logged online:
Bug reference: 3571
Logged by: Ken Colson
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.9
Operating system: centOS 64 bit (Linux 2.6.18-8.1.6.el5)
Description:call to decrypt causes segfault
Details:
this statemen
Randolf Richardson wrote:
> After convincing clients and colleagues to switch from Oracle (and
> others) to PostgreSQL, an issue that comes up is the need to
> customize DATESTYLE. Because this isn't possible,
Sure it's possible. You replace the respective data type output
functions with somethi
Julius Stroffek <[EMAIL PROTECTED]> writes:
> pgbench contrib module is doing segmentation fault on Solaris
> when -d option is specified without -p option specified.
Applied in HEAD and 8.2. Thanks for the report!
regards, tom lane
---(end of bro
"Ken Colson" <[EMAIL PROTECTED]> writes:
> this statement:
> select decrypt(''::bytea,'password','bf')
> causes the postgresql backend to crash:
> This seems to be a 64bit problem.
Reproduced here in HEAD. The problem is here:
Program terminated with signal 11, Segmentation fault.
#0 0x2aaa
16 matches
Mail list logo
