m
303-955-0509
===
On Tue, Aug 23, 2011 at 5:46 PM, Adrian Klaver wrote:
> On Tuesday, August 23, 2011 3:47:33 pm Sam Nelson wrote:
>> Hi list,
>>
>> A client is hitting an issue with JDBC:
>> org.postgresql.util.PSQLException: Connection refused
Hi list,
A client is hitting an issue with JDBC:
org.postgresql.util.PSQLException: Connection refused. Check that the
hostname and port are correct and that the postmaster is accepting
TCP/IP connections.
-pg_hba.conf is set to trust 0.0.0.0/0 (IPv4 only)
-listen_addresses is *
-I can find no ev
Hi, List,
We're trying to calculate the amount of time that a Hot Standby slave is
lagging behind its master, and our results look wrong (average of 7 seconds,
with some over 1 minute), so we were thinking that we're probably
calculating it wrong.
We're currently just using the timestamps from ls
n Moncure wrote:
>
>> On Thu, May 5, 2011 at 12:13 PM, Sam Nelson
>> wrote:
>> > Hi List,
>> > We have a customer who is trying to migrate a few PostgresPlus instances
>> to
>> > GridSQL clusters. They have a process that pulls data from another
>&g
Hi List,
We have a customer who is trying to migrate a few PostgresPlus instances to
GridSQL clusters. They have a process that pulls data from another server
using dblink every night, and we're trying to replicate that on the GridSQL
instance, but grid is being a bit of a pain.
Grid doesn't see
more info than
that. We're quite busy and my ability to remember things is ...
questionable.
-Sam
On Thu, Sep 9, 2010 at 8:14 AM, Merlin Moncure wrote:
> On Wed, Sep 8, 2010 at 6:55 PM, Sam Nelson
> wrote:
> > Even if the corruption wasn't a result of that, we weren&#
with many more
questions.
-Sam
On Wed, Sep 8, 2010 at 2:58 PM, Tom Lane wrote:
> Merlin Moncure writes:
> > On Wed, Sep 8, 2010 at 4:03 PM, Sam Nelson
> wrote:
> >> So ... yes, it seems that those four id's are somehow part of the
> problem.
> >> They&
y to remember to write back with
whether or not any of those things worked.
On Wed, Sep 8, 2010 at 1:30 PM, Tom Lane wrote:
> Sam Nelson writes:
> > pg_dump: Error message from server: ERROR: invalid memory alloc request
> > size 18446744073709551613
> > pg_dump: The com
Hey, a client of ours has been having some data corruption in their
database. We got the data corruption fixed and we believe we've discovered
the cause (they had a script killing any waiting queries if the locks on
their database hit 1000), but they're still getting errors from one table:
pg_dum
Alright, well, we'll probably do something with the archive command, then,
like either echoing %f to a log file or sending that to syslog (and then,
after the echo, doing the actual cp or scp or rsync or whatever). That way,
we should be able to get some form of timestamp of when each WAL file is
Is there a way to get postgres to write a line to the log file when it
creates a WAL file? We wrote a script that tries to grab the times between
WAL file creation and ingestion without stopping to make absolutely sure
that postgres actually logs the WAL file creation, and so we're kinda stuck
sta
Wow. I must be blind. Or brain dead.
You're right. That was the issue.
-Sam
On Thu, Aug 19, 2010 at 9:22 PM, Tom Lane wrote:
> Sam Nelson writes:
> > Here's the output from pg_controldata:
>
> > $ pg_controldata `pwd`
> > WARNING: Calculated CRC check
if they've done anything weird with the database
in the last while.
Thanks for your help.
-Sam
On Thu, Aug 19, 2010 at 5:14 PM, Tom Lane wrote:
> Sam Nelson writes:
> >> It's almost certainly not ruby's fault. Have they done anything
> >> strange like kill
Let me preface this by saying that I've set up warm standby instances quite
a few times. I think I sort of hopefully know what I'm doing.
pg_start_backup('stuff'), tar data directory, pg_stop_backup(), copy data
directory to warm standby server, extract in data directory, etc.
We have two CentOS
Sorry, I forgot to mention that we also tried reindexing the toast table.
On Thu, Aug 19, 2010 at 1:20 PM, Scott Marlowe wrote:
> SNIP
>
> It's almost certainly not ruby's fault. Have they done anything
> strange like kill the instance and restart it without letting the db
> shut down? I'd tend
Good morning, list.
We've got a bit of a problem on a customer's production box. We got a
"missing chunk number 0 for toast value N" (N being a number) this week on
their production box. We verified that it was only a problem with one row,
tried to fix it with updates, and ended up deleting the
16 matches
Mail list logo
