Hi
Our scripts automatically add "LIMIT ALL" & "OFFSET 0" to every select
query if no values are passed on for these parameters. I remember reading
through the mailing list that it's better not to pass them if they are not
needed as they add a cost to the query plan. Is this the case, or am i
loo
On Tue, Nov 22, 2011 at 11:41 PM, Bruce Momjian wrote:
> Amitabh Kant wrote:> >
> >
> > On a slightly unrelated note, you had once (
> > http://archives.postgresql.org/pgsql-general/2011-08/msg00944.php) said
> to
> > limit shared_buffers max to 8 G
On Fri, Nov 18, 2011 at 3:39 PM, Greg Smith wrote:
> On 11/17/2011 10:44 PM, CSS wrote:
>
>> Is there any sort of simple documentation on the query planner that might
>> cover how things like increased RAM could impact how a query is executed?
>>
>
> There is no *simple* documentation on any part
10 series rather than 320 (pay for them with the
> money saved from #3 above). Those devices have much, much higher specified
> endurance than the 320s and since your DB is quite small you only need to
> buy one of them.
>
>
> On 10/24/2011 8:09 AM, Amitabh Kant wrote:
>
>>
Thanks Jeff. This should help in getting a fairly approximate values.
Amitabh
On Fri, Oct 28, 2011 at 11:24 AM, Jeff Davis wrote:
> On Mon, 2011-10-24 at 19:34 +0530, Amitabh Kant wrote:
> > If I read the xact_commit field returned by "Select * from
> > pg_stat_database&
Hello
I need to choose between Intel 320 , Intel 510 and OCZ Vertex 3 SSD's for my
database server. From recent reading in the list and other places, I have
come to understand that OCZ Vertex 3 should not be used, Intel 510 uses a
Marvel controller while Intel 320 had a nasty bug which has been re
If I read the xact_commit field returned by "Select * from pg_stat_database"
multiple times, and then average the difference between consecutive values,
would this give an approx idea about the transactions per second in my
database?
Does this figure include the number of select statements being e
On Wed, Feb 10, 2010 at 9:39 AM, Jayadevan M
wrote:
> Any feedback - a few sentences with the db size, tps, h/w necessary to
> support that, and acceptable down-time, type of application etc will be
> greatly appreciated.
> Our products are not of the blog/social networking type, but more of
> o
wn
> the hardware tech to confirm, and he's out today. System has 16
> Xeon CPUs and 64 GB RAM.
>
> -Kevin
>
>
Hi Kevin
Just curious if you have a 16 physical CPU's or 16 cores on 4 CPU/8 cores
over 2 CPU with HT.
With regards
Amitabh Kant
On Thu, Feb 4, 2010 at 3:29 AM, Greg Smith wrote:
> Robert Haas wrote:
>
> On Wed, Feb 3, 2010 at 10:10 AM, Amitabh Kant
> wrote:
>
>
> work_mem = 160MB # pg_generate_conf wizard 2010-02-03
>
>
> Overall these settings look sane, but this one looks like an
>
On Thu, Feb 4, 2010 at 3:10 PM, Ivan Voras wrote:
> On 4 February 2010 10:02, Amitabh Kant wrote:
> > On Wed, Feb 3, 2010 at 10:05 PM, Ivan Voras wrote:
> >>
> >> On 02/03/10 16:10, Amitabh Kant wrote:
> >>>
> >>> Hello
> >>>
On Thu, Feb 4, 2010 at 12:11 AM, Andy Colson wrote:
> On 2/3/2010 9:10 AM, Amitabh Kant wrote:
>
>> Hello
>>
>> I have a server dedicated for Postgres with the following specs:
>>
>> RAM 16GB, 146GB SAS (15K) x 4 - RAID 10 with BBU, Dual Xeon E5345 @
&g
On Wed, Feb 3, 2010 at 10:05 PM, Ivan Voras wrote:
> On 02/03/10 16:10, Amitabh Kant wrote:
>
>> Hello
>>
>> I have a server dedicated for Postgres with the following specs:
>>
>> RAM 16GB, 146GB SAS (15K) x 4 - RAID 10 with BBU, Dual Xeon E5345 @
>>
On Wed, Feb 3, 2010 at 9:49 PM, Reid Thompson wrote:
> On Wed, 2010-02-03 at 20:42 +0530, Amitabh Kant wrote:
> > Forgot to add that I am using Postgres 8.4.2 from the default ports of
> > FreeBSD.
>
> start with this page
> http://www.postgresql.org/docs/8.4/static/ker
appreciate if somebody could point out the sysctl/loader.conf
settings that I need to have in FreeBSD.
With regards
Amitabh Kant
Forgot to add that I am using Postgres 8.4.2 from the default ports of
FreeBSD.
With regards
Amitabh Kant
On Wed, Feb 3, 2010 at 8:40 PM, Amitabh Kant wrote:
> Hello
>
> I have a server dedicated for Postgres with the following specs:
>
> RAM 16GB, 146GB SAS (15K) x 4 - R
o changes that I can suggest in your hardware would be to go in for SAS
15K disks instead of SATA if you can do with less capacity, and goign in for
RAID 10 instead of RAID 5.
Regards
Amitabh Kant
17 matches
Mail list logo
