Hello,Couple of questions:1. For the 'Asynchronous commit' mode, I know that
WAL transactions not flushed to permanent storage will be lost in event of a
server crash. Is it possible to know what were the non-flushed transactions
that were lost, in any shape/form/part ? I guess not, but wanted
l.com
> CC: pgsql-admin@postgresql.org
>
> On Thu, May 20, 2010 at 10:54 AM, Balkrishna Sharma wrote:
> > I need to support several hundreds of concurrent update/inserts from an
> > online form with pretty low latency (maybe couple of milliseconds at max).
> > Think of
systems. hard
> drives and bbu RAID are proven solutions, SSD is still not really
> there just yet in terms of being proven reliable.
>
> On Thu, May 20, 2010 at 1:02 PM, Balkrishna Sharma wrote:
> > Good suggestion. Thanks.
> > What's your take on SSD ?
to be written out due to issues with the
> fact that it cannot write small blocks one at a time but needs to
> write large chunks together at once.
>
> On Thu, May 20, 2010 at 2:10 PM, Balkrishna Sharma wrote:
> > What if we don't rely on the cache of SSD, i.e. have write
Hello,
How does postgres perform with large object (pdf,word docs,images,mp3,mp4)
storage ? For my system, individual object size will be at max a few MBs with
most objects being less than a MB. Also between "TOAST" and "large objects"
what is more preferred ?What are the other alternatives (fi
Hi,
I am increasing the shared_buffer size in postgresql.conf and want to measure
its effect on READ. In essence I want to know if the SELECT queries I am firing
repeatedly is reading from the buffer or going directly to the disk.
I am expecting the first SELECT to go to disk and the subsequent
Hi,
I am having a transactional database heavy on parallel reads and updates. Apart
from hardware optimization, I want to ensure that my system parameters are
optimized as well. Following is what I am doing on my test system having 4GB
RAM. Please let me know if the logic sounds ok (at least at
I am on Fedora 12 (x86_64). Will eventually be on RHE.
> Date: Tue, 25 May 2010 12:59:16 -0500
> From: kevin.gritt...@wicourts.gov
> To: b...@hotmail.com; pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] How to find if a SELECT is reading from buffer or
> disk ?
>
&
Hello,
In PostgreSQL 9.x, using Streaming replication (hot standby with PITR), is it
possible to have just the standby server in Cloud(Amazon) and the primary
database local ?What I am trying to achieve is get the backups guaranteed in
cloud, if I just have my standby server there ?
Is it techn
If the database is not extremely huge, makes you wonder what does a RAID
actually give us. A robust near-realtime replication setup (say PITR + cloud)
may be good enough against once in a few years of disk failure.atleast you
don't add another point of failure that you (your database/OS) can't
.@wicourts.gov
> To: b...@hotmail.com; pgsql-admin@postgresql.org; q...@vp.pl
> Subject: Re: [ADMIN] db recovery after raid5 failure
>
> Balkrishna Sharma wrote:
>
> > If the database is not extremely huge, makes you wonder what does
> > a RAID actually give us.
>
I know that we can toggle the timing at session level by using \timing in psql.
Is there a way to set the default to 'timing on' globally across the database
or atleast across all psql statements by a specificied user ?
Thanks,-Bala
__
Thanks. If I want to do at system-wide level, where do I store the psqlrc file
(assuming I want to change the timing behavior system-wide)?
(CentOS 5, Postgres 8.4)
$ ./pg_config --sysconfdir/opt/PostgreSQL/8.4/etc/postgresql
But I don't have /opt/PostgreSQL/8.4/etc/postgresql directory. Just cre
de the client machines) somewhere on the server so that psql -c on client
would capture the timing automatically.
> From: br...@momjian.us
> Subject: Re: [ADMIN] Change to 'timing on' globally
> To: b...@hotmail.com
> Date: Tue, 6 Jul 2010 10:48:48 -0400
> CC: alvhe...@comma
14 matches
Mail list logo
