Hello and greetings,
I need help in understanding the purpose of the following columns produced by
PG stats collector in version 9.1
>From pg_stat_database
-
blks_read,
blks_hit,
_tup_returned,
tup_fetched
Reported In pg_stat_user_tables
-
For such things documentation is your best friend. Please see inline.
On Sun, May 12, 2013 at 4:30 PM, Arvind Singh wrote:
> I need help in understanding the purpose of the following columns produced
> by PG stats collector in version 9.1
>
> From pg_stat_database
>
That option doesn't seem to exist, but pg_basebackup does seem to be the
way to go.
Thanks for the help, Jeff!
On Sat, May 11, 2013 at 2:15 PM, Jeff Janes wrote:
> On Sat, May 11, 2013 at 7:56 AM, Moshe Jacobson wrote:
>
>> I have a master database cluster on one server, and it is configured to
On 5/11/2013 3:10 AM, Matt Brock wrote:
On 10 May 2013, at 16:25, David Boreham wrote:
I've never looked at SLC drives in the past few years and don't know anyone who
uses them these days.
Because SLCs are still more expensive? Because MLCs are now almost as good as
SLCs for performance/end
On 5/12/2013 6:13 PM, David Boreham wrote:
Not quite. More like : a) I don't know where to buy SLC drives in 2013
(all the drives for example for sale on newegg.com are MLC) and b)
today's MLC drives are quite good enough for me (and I'd venture to
say any database-related purpose).
Newegg
btw we deploy on CentOS6. The only things we change from the default are:
1. add "relatime,discard" options to the mount (check whether the most
recent CentOS6 does this itself -- it didn't back when we first deployed
on 6.0).
2. Disable swap. This isn't strictly an SSD tweak, since we have en
On 5/12/2013 7:20 PM, John R Pierce wrote:
the real SLC drives end up OEM branded in large SAN systems, such as
sold by Netapp, EMC, and are made by companies like STEC that have
zero presence in the 'whitebox' resale markets like Newegg.
Agreed. I don't go near the likes of Simple, HGST,
On 5/12/2013 6:41 PM, David Boreham wrote:
Agreed. I don't go near the likes of Simple, HGST, F-IO, SMART, et al.
For me this is SAS and SCSI re-born -- an excuse to charge very high
prices for a product not significantly different from a much cheaper
mainstream alternative, by exploiting unsop
Hello,
Currently, we are developing some tool for PostgreSQL. To determine the
functional specification, I would like to ask PostgreSQL users about the
necessity of support for the -U option of initdb.
In what situations do you use -U option of initdb? Is it essential for what
reason?
I'm n
Package systems which create an automatic user account for your
postgresql instance, for example in OpenBSD:
system user: _postgresql (in accordance to OpenBSD ports rules)
db user: postgres
I always use:
initdb -U postgres
Because that's what everyone expects it to be...
On Sun, May 12, 2013
> However, PG documentation doesn't highlight about this in psql or PAM
> section, because log entries written are slightly confusing.
> http://www.postgresql.org/docs/9.2/static/auth-methods.html
> http://www.postgresql.org/docs/9.2/static/app-psql.html
It turns out this logging is a bug in PAM a
11 matches
Mail list logo
