On 10/23/2012 01:20 PM, Tom Lane wrote:
>
> This isn't the first time I've wondered exactly which signal was meant
> in a postmaster child-crash report. Seems like it might be worth
> expending some code on a symbolic translation, instead of just printing
> the number. That'd be easy enough (for
Craig Ringer writes:
> On 10/22/2012 08:52 PM, Tom Lane wrote:
>> But having said that, are we sure 10 is SIGUSR1 on the OP's platform?
>> AFAIK, that signal number is not at all compatible across different
>> flavors of Unix. (I see SIGUSR1 is 30 on OS X for instance.)
> Gah. I incorrectly thou
On 10/22/2012 08:52 PM, Tom Lane wrote:
> Craig Ringer writes:
>> On 10/19/2012 04:40 PM, raghu ram wrote:
>>> 2012-10-19 12:26:46 IST [1338]: [18-1] user=,db= LOG: server process
>>> (PID 15565) was terminated by signal 10
>
>> That's odd. SIGUSR1 (signal 10) shouldn't terminate PostgreSQL.
>
On Mon, Oct 22, 2012 at 7:17 AM, Chris Angelico wrote:
> After reading the comments last week about SSDs, I did some testing of
> the ones we have at work - each of my test-boxes (three with SSDs, one
> with HDD) subjected to multiple stand-alone plug-pull tests, using
> pgbench to provide load. S
On Monday, October 22, 2012 05:55:07 PM Nikolas Everett wrote:
> I was just looking at
> http://www.postgresql.org/docs/devel/static/release-9-2.html and it
> mentioned that a dump/reload cycle was required to upgrade from a previous
> release. I just got done telling some of my coworkers that PG
pg_upgrade has worked fine for several releases. I believe that the
only time when pg_upgrade isn't a viable option is for some types of
GIST indices.
On Mon, Oct 22, 2012 at 2:55 PM, Nikolas Everett wrote:
> I was just looking at
> http://www.postgresql.org/docs/devel/static/release-9-2.html an
I was just looking at
http://www.postgresql.org/docs/devel/static/release-9-2.html and it
mentioned that a dump/reload cycle was required to upgrade from a previous
release. I just got done telling some of my coworkers that PG had been
bitten by this enough times that they were done with it. Am I
On Mon, Oct 22, 2012 at 11:54:47AM +0200, Heiko Wundram wrote:
> If there's any other possibility of "out of the box" recovery -
> except writing myself a small script to walk all rows - I'd still be
> grateful for a hint.
Something that has worked for me in the past is:
$ SELECT ctid FROM table
On Mon, Oct 22, 2012 at 12:31 PM, Chris Angelico wrote:
> On Tue, Oct 23, 2012 at 6:26 AM, Jeff Janes wrote:
>> What did you do to look for corruption? That PosgreSQL succeeds at
>> going through crash-recovery and then starting up is not a good
>> indicator that there is no corruption.
>
> I fi
On Tue, Oct 23, 2012 at 6:26 AM, Jeff Janes wrote:
> What did you do to look for corruption? That PosgreSQL succeeds at
> going through crash-recovery and then starting up is not a good
> indicator that there is no corruption.
I fired up Postgres and looked at the logs for any signs of failure.
On Mon, Oct 22, 2012 at 6:17 AM, Chris Angelico wrote:
> After reading the comments last week about SSDs, I did some testing of
> the ones we have at work - each of my test-boxes (three with SSDs, one
> with HDD) subjected to multiple stand-alone plug-pull tests, using
> pgbench to provide load. S
On Mon, Oct 22, 2012 at 7:52 AM, Albe Laurenz wrote:
> Hannes Erven wrote:
>> today I ran into an issue I believed to be a FAQ, but fortunately it
>> doesn't seem so as I could find any resources related to this... :-/
>>
>> A misguided click in PGADMIN executed a "TRUNCATE CASCADE" on a rather
>>
Hi all,
I am currently running Postgresql 9.2.1 with streaming replication: one
primary, one standby. Once an hour I have a job which compares
pg_current_xlog_location on the primary against
pg_last_xlog_replay_location on the standby to ensure the standby is not
lagging too far behind the primar
Well..
There should be a standby server ready to server as a primary if the current
primary goes down right ??
But the dead primary is yet in the mode of configuring stage or probably
failed to be a standby server.
In my high availability cluster there are only two servers.
--Reddy.
--
Vie
On Mon, Oct 22, 2012 at 7:47 PM, Vishalakshi Navaneethakrishnan
wrote:
> Hi all,
>
> I need to know who are all access database from different remote host.
>
> Example :
>
> User1@host1 logged / access db dbuser@dbname in Dbserver
>
> How can i get this information?
As suggested, you can configu
chinnaobi wrote:
> I have tested using cygwin rsync in windows 2008 R2, just after
restart the
> server.
>
> for 10 GB it took nearly 5 minutes to sync,
> for 50 GB it took nearly 30 minutes, -- too long Though there were no
big
> changes.
>
> My requirement is something less than 5 minutes. I a
Hi Laurenz Albe,
I have tested using cygwin rsync in windows 2008 R2, just after restart the
server.
for 10 GB it took nearly 5 minutes to sync,
for 50 GB it took nearly 30 minutes, -- too long Though there were no big
changes.
My requirement is something less than 5 minutes. I am doing high
av
After reading the comments last week about SSDs, I did some testing of
the ones we have at work - each of my test-boxes (three with SSDs, one
with HDD) subjected to multiple stand-alone plug-pull tests, using
pgbench to provide load. So far, there've been no instances of
PostgreSQL data corruption,
Hannes Erven wrote:
> today I ran into an issue I believed to be a FAQ, but fortunately it
> doesn't seem so as I could find any resources related to this... :-/
>
> A misguided click in PGADMIN executed a "TRUNCATE CASCADE" on a rather
> central table of my schema, which resulted in most importan
Craig Ringer writes:
> On 10/19/2012 04:40 PM, raghu ram wrote:
>> 2012-10-19 12:26:46 IST [1338]: [18-1] user=,db= LOG: server process
>> (PID 15565) was terminated by signal 10
> That's odd. SIGUSR1 (signal 10) shouldn't terminate PostgreSQL.
> Was the server intentionally sent SIGUSR1 by an
Hi all,
today I ran into an issue I believed to be a FAQ, but fortunately it
doesn't seem so as I could find any resources related to this... :-/
A misguided click in PGADMIN executed a "TRUNCATE CASCADE" on a rather
central table of my schema, which resulted in most important tables
being
Am 22.10.2012 09:05, schrieb Craig Ringer:
Working strictly with a *copy*, does REINDEXing then CLUSTERing the
tables help? VACCUM FULL on 8.3 won't rebuild indexes, so if index
damage is the culprit a reindex may help. Then, if CLUSTER is able to
rewrite the tables in index order you might be ab
Rob wrote:
> Some more info
> Oracle Server:Oracle 11g R2 (11.2.0.2.0)
> Client: 11.2
> Was installed using Oracle Universal Installer
Ok.
> I don't really want to post the full environment of the postmaster but
> basically I could see no entry in there for ORACLE_HOME or TNS_ADMIN,
should
> I?
On Mon, Oct 22, 2012 at 2:17 PM, Vishalakshi Navaneethakrishnan <
nvishalak...@sirahu.com> wrote:
> Hi all,
>
> I need to know who are all access database from different remote host.
>
> Example :
>
> User1@host1 logged / access db dbuser@dbname in Dbserver
>
> How can i get this information?
>
>
Hi all,
I need to know who are all access database from different remote host.
Example :
User1@host1 logged / access db dbuser@dbname in Dbserver
How can i get this information?
Thanks in advance..
--
Best Regards,
Vishalakshi.N
On 10/19/2012 10:31 PM, Heiko Wundram wrote:
> Hey!
>
> I'm currently in the situation that due to (probably) broken memory in a
> server, I have a corrupted PostgreSQL database. Getting at the data
> that's in the DB is not time-critical (because backups have restored the
> largest part of it), b
On 10/19/2012 04:40 PM, raghu ram wrote:
> Hi All,
>
> We have configured Streaming Replication b/w Primary and Standby server
> and Pgpool-II load balancing module diverting
> SELECT statements to Standby server. As per our observations, Standby
> server crashed during peak hours on today and er
27 matches
Mail list logo
