"Luiz Henrique" <[EMAIL PROTECTED]> writes:
> On 8/21/06, Jim Nasby <[EMAIL PROTECTED]> wrote:
>> What version are you using? In recent versions, indexes are supposed
>> to be safe from corruption, even through crashes.
> It's Postgresql 7.2.1, installed with stable version of Debian Woody, at the
[ redirecting to pgsql-hackers since this is not a bug ]
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> Manuel A. Fernandez Montecelo wrote:
>> Well, I use around 10 libraries in my project, it's easier to use
>> standardized
>> methods to gather the compiler/linker options using pkg-config than c
This probably isn't a bug. Make sure your database server is configured to use TCP/IP and that there is no firewall blocking connections.On Aug 22, 2006, at 8:20 AM, Sunil Kumar Basu wrote:The following bug has been logged online:Bug reference: 2587Logged by: Sunil Kumar BasuEmail ad
Manuel A. Fernandez Montecelo wrote:
>
> Well, I use around 10 libraries in my project, it's easier to use
> standardized
> methods to gather the compiler/linker options using pkg-config than calling
> different configuration scripts for each one, and using "pkg-config --exists
> $name" or "pk
It's Postgresql 7.2.1, installed with stable version of Debian Woody, at the time.On 8/21/06, Jim Nasby <[EMAIL PROTECTED]
> wrote:On Aug 15, 2006, at 8:50 AM, Luiz Henrique wrote:> my problem was problably corrupted index files. I recreated the
> index and it's ok now. The hardware was being unplu
The following bug has been logged online:
Bug reference: 2587
Logged by: Sunil Kumar Basu
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0
Operating system: Windows XP
Description:Connection problem
Details:
Hi,
I am installed PostgreSQL 8.0 database server
Well, I use around 10 libraries in my project, it's easier to use standardized
methods to gather the compiler/linker options using pkg-config than calling
different configuration scripts for each one, and using "pkg-config --exists
$name" or "pkg-config --at-least=1.0 $name" than to check wheth
On Aug 15, 2006, at 8:50 AM, Luiz Henrique wrote:
my problem was problably corrupted index files. I recreated the
index and it's ok now. The hardware was being unpluged from power
source without shuthing down, I guess that's the cause.
What version are you using? In recent versions, indexes
