On 06-01-2012 15:16, max.k...@atip.de wrote:
> FATAL: requested recovery stop point is before consistent recovery point.
>
> One system is configured as standby, performing stream and WAL replication.
> Another system is running in primary mode.
> I have verified that the standby system performed
sree...@ordyn.com writes:
> When I give "SELECT extract(epoch from now() );" the output is
> 1325872658.xxx
> I would expect a slightly incremented value when after a few seconds I give
> the command "SELECT extract(epoch from now() at time zone 'utc+05:30');" .
> Nut I get the value 1325833067.x
On 7/01/2012 12:01 PM, golod...@mail.ru wrote:
The following bug has been logged on the website:
Bug reference: 6387
Logged by: golodnew
Email address: golod...@mail.ru
PostgreSQL version: 9.1.1
Operating system: windows xp
Description:
can't connect to postgres sql (wrong
On 8/01/2012 12:23 AM, stoian_cris2...@yahoo.com wrote:
Connection to database failed: -->could not connect to server: Connection
refused (0x274D/10061)
Is the server running on host "127.0.0.1" and accepting
TCP/IP connections on port 5432?
<--error
WHAT CAN I DO ?
Hi Tom,
Thanks for the solution. CIFS worked with fsync flag by ingnoring EINVAL in
copydir.c.
I tested fsync with 8.2.2 version of PostgreSQL, it worked fine without EINVAL
patch. I wanted to know is something changed in version 9.0.4 of postgreSQL.
As fsync flag was not working with Post
