I generally use Ontrack EasyRecovery Professional for recovering deleted
or data sitting in bad sectors from hard drives in windows. It's not
free, but it works really well.
I have had issues with Symantec BackupExec causing PostgreSQL to panic
and shutdown when data is being inserted into tab
I've had the same problem with server 2003. I usually create the folder where
PostgreSQL is going to install into first, then change the permissions for
"\users" to full control before attempting to install.
-Original Message-
From: pgsql-bugs-ow...@postgresql.org [mailto:pgsql-bugs-ow..
I force postgresql to use indexes instead of sequential scans by setting
enable_seqscan = off in postgresql.conf and it helps in a lot of cases.
Probably not the best practice, but it does improve a lot of the queries
we will execute on a regular basis. It forces the planner to prefer
indexes. I've
l character.
-Original Message-
From: pgsql-bugs-ow...@postgresql.org [mailto:pgsql-bugs-ow...@postgresql.org]
On Behalf Of Nathan M. Davalos
Sent: Wednesday, March 23, 2011 7:59 PM
To: PostgreSQL Bugs
Subject: Re: [BUGS] BUG #5944: COPY FROM doesn't work with international
charac
ssage-
From: John R Pierce [mailto:pie...@hogranch.com]
Sent: Wednesday, March 23, 2011 7:54 PM
To: Nathan M. Davalos; PostgreSQL Bugs
Subject: Re: [BUGS] BUG #5944: COPY FROM doesn't work with international
characters
On 03/23/11 5:42 PM, Nathan M. Davalos wrote:
> Just in case the reply didn&
32333030303209416C746F20446573656D7065F16F2C20532E412E20446520432E562E0D0A
The character in question is F1
-Original Message-
From: John R Pierce [mailto:pie...@hogranch.com]
Sent: Wednesday, March 23, 2011 6:49 PM
To: Nathan M. Davalos
Cc: pgsql-bugs@postgresql.org
Subject: Re: [BUGS
I ran into something interesting with using trunc() and different data
types:
The following is a simplified from the statement we're using and
produces the same results:
select trunc( ((cast(2183.68 as numeric) - cast(1 as numeric)) )*100)
/100
yields 2184.68
select trunc(((cast(2183.6
