Leonid,System Event Viewer has the follwoing entries:1. The PostgreSQL Database Server
8.1 service was successfully sent a startcontrol.2. The PostgreSQL Database Server 8.1 service entered the running state.3. The PostgreSQL Database Server 8.1 service entered the stopped state.
please look insid
Hi All,
It doesn't appear that ANALYZE uses the specified operator class for
producing statistics on an index when that operator class is not the
default for the data type. This appears to be leading to poor query
planning.
I'm using:
# select version();
-[ RECORD
1 ]-
On Tue, 2006-10-31 at 23:18 -0500, Tom Lane wrote:
> Jeff Davis <[EMAIL PROTECTED]> writes:
> > Is this not a bug?
>
> I don't actually see that it is. The documentation is perfectly clear
> on the point:
>
> (It is your responsibility that the byte sequences you create
> are valid c
Tom Lane skrev:
Is this not a bug?
I don't actually see that it is. The documentation is perfectly clear
on the point:
(It is your responsibility that the byte sequences you create
are valid characters in the server character set encoding.)
(This is in 4.1.2.1. String Consta
>> but again to_date doesn't:
>>
>> regression=# select to_date('4714-01-27 BC', '-MM-DD BC');
>> to_date
>> ---
>> 4714-01-27 BC
>> (1 row)
>>
>
> I'm not concerned about to_date so much as I am that timestamp_in lets you
> store values you can't read with timestamp_out. O
"Marcio" <[EMAIL PROTECTED]> writes:
> I have a sugestion for pgsql 8.2 or next versions ...
> Is complicated encrypt the procedures/functions on Database like Oracle or
> similar?
> I sugest this because we develop ERP/MRP with complex routines and we like
> hide all of this routines...this is ou
>
> postgres=# select '4714-01-27 BC'::date;
> ERROR: date out of range: "4714-01-27 BC"
> postgres=# select cast(test as date) from timetest;
> test
> ---
> 4714-01-27 BC
> (1 row)
>
> postgres=#
> postgres=# select cast('4714-01-27 BC' as date);
> ERROR: date out of range: "
The following bug has been logged online:
Bug reference: 2731
Logged by: Leonid Shlyapnikov
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.5-1
Operating system: Windows XP Media Center Edition Version 2002 Service
Pack 2
Description:Cannot install PostgreSQL
The following bug has been logged online:
Bug reference: 2734
Logged by: Wagner Cipriano
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0
Operating system: linux SUSE Kernel 2.6.13.3
Description:Primary Key field duplicate value
Details:
I Have a table 'clie
The following bug has been logged online:
Bug reference: 2733
Logged by: Basil Evseenko
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2beta2
Operating system: Linux 2.6
Description:pg_get_serial_sequence error (addition: may be tsearch2
related)
Details:
On
The following bug has been logged online:
Bug reference: 2732
Logged by: Basil Evseenko
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2beta2
Operating system: Linux 2.6
Description:pg_get_serial_sequence error
Details:
On 8.1.5:
select pg_catalog.pg_get_se
Andreas Lange <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> I suppose there is something funny about pow() on your platform
>> causing that probe to fail. What does config.log have at the
>> "checking for library containing pow" step?
>>
> configure:5168: checking for library containing pow
>
Tom Lane wrote:
configure:13462: checking for cbrt
configure:13519: /sw/sun-studio-11/SUNWspro/bin/cc -Xa -o conftest -fast
-fns=no -fsimple=1 -xtarget=opteron -xarch=amd64a conftest.c -lz
-lrt -lsocket >&5
"conftest.c", line 104: warning: statement not reached
Undefined
Alvaro Herrera wrote:
Andreas Lange wrote:
configure:13462: checking for cbrt
configure:13519: /sw/sun-studio-11/SUNWspro/bin/cc -Xa -o conftest -fast
-fns=no -fsimple=1 -xtarget=opteron -xarch=amd64a conftest.c -lz
-lrt -lsocket >&5
"conftest.c", line 104: warning: statement
Andreas Lange <[EMAIL PROTECTED]> writes:
> configure:13462: checking for cbrt
> configure:13519: /sw/sun-studio-11/SUNWspro/bin/cc -Xa -o conftest -fast
> -fns=no -fsimple=1 -xtarget=opteron -xarch=amd64a conftest.c -lz
> -lrt -lsocket >&5
> "conftest.c", line 104: warning: statement not reac
Andreas Lange wrote:
> configure:13462: checking for cbrt
> configure:13519: /sw/sun-studio-11/SUNWspro/bin/cc -Xa -o conftest -fast
> -fns=no -fsimple=1 -xtarget=opteron -xarch=amd64a conftest.c -lz
> -lrt -lsocket >&5
> "conftest.c", line 104: warning: statement not reached
> Undefined
Alvaro Herrera wrote:
Andreas Lange wrote:
And here is from configure:
checking whether gettimeofday takes only one argument... no
checking for cbrt... no
Undoubtely this is the problem. Can you show the relevant config.log
extract?
Ok, here we go:
configure:134
Marcio wrote:
> Is complicated encrypt the procedures/functions on Database like
> Oracle or similar?
In order to execute the code you will have to be able to read it, so
there will be no security gained by encryption.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
--
Andreas Lange wrote:
> And here is from configure:
>
> checking whether gettimeofday takes only one argument... no
> checking for cbrt... no
Undoubtely this is the problem. Can you show the relevant config.log
extract?
--
Alvaro Herrerahttp://www.CommandPrompt.
Hi,
I have problems building 8.2beta2 on a Solaris 10 x86-64 machine:
gmake[4]: Entering directory
`/files/dsk1/lsw/src/postgresql/postgresql-8.2beta2/src/backend/utils/adt'
/sw/sun-studio-11/SUNWspro/bin/cc -Xa -fast -fns=no -fsimple=1
-xtarget=opteron -xarch=amd64a -I../../../../src/include -
I have a sugestion for pgsql 8.2 or next versions ...
Is complicated encrypt the procedures/functions on Database like Oracle or
similar?
I sugest this because we develop ERP/MRP with complex routines and we like
hide all of this routines...this is our "business secret".
I know if we write this co
21 matches
Mail list logo
