Skip site navigation (1) Skip section navigation (2)

Re: IN question

From: "Mat Caughron" <caughron(at)gmail(dot)com>
To: "Josh Berkus" <josh(at)agliodbs(dot)com>
Cc: "Meredith L(dot) Patterson" <mlp(at)thesmartpolitenerd(dot)com>, sfpug(at)postgresql(dot)org
Subject: Re: IN question
Date: 2008-12-16 23:22:00
Message-ID: d5aeb68a0812161522n62626d48oc4102fad76f074a@mail.gmail.com (view raw or flat)
Thread:
Lists: sfpug
All:

In the interest of investigating various throughput limits.
Where do we get cache and buffer and heap size limitations, and how to set
these?
Is there something similar in postgres-world to the mysql-world equivalent
of the following:



mysql> show variables like '%size%';
+---------------------------------+------------+
| Variable_name                   | Value      |
+---------------------------------+------------+
| bdb_cache_size                  | 8388600    |
| bdb_log_buffer_size             | 32768      |
| binlog_cache_size               | 32768      |
| bulk_insert_buffer_size         | 8388608    |
| delayed_queue_size              | 1000       |
| innodb_additional_mem_pool_size | 1048576    |
| innodb_buffer_pool_size         | 8388608    |
| innodb_log_buffer_size          | 1048576    |
| innodb_log_file_size            | 5242880    |
| join_buffer_size                | 131072     |
| key_buffer_size                 | 8388600    |
| key_cache_block_size            | 1024       |
| max_binlog_cache_size           | 4294967295 |
| max_binlog_size                 | 1073741824 |
| max_heap_table_size             | 16777216   |
| max_join_size                   | 4294967295 |
| max_relay_log_size              | 0          |
| myisam_data_pointer_size        | 4          |
| myisam_max_extra_sort_file_size | 2147483648 |
| myisam_max_sort_file_size       | 2147483647 |
| myisam_sort_buffer_size         | 8388608    |
| preload_buffer_size             | 32768      |
| query_alloc_block_size          | 8192       |
| query_cache_size                | 0          |
| query_prealloc_size             | 8192       |
| range_alloc_block_size          | 2048       |
| read_buffer_size                | 131072     |
| read_rnd_buffer_size            | 262144     |
| sort_buffer_size                | 2097144    |
| thread_cache_size               | 0          |
| tmp_table_size                  | 33554432   |
| transaction_alloc_block_size    | 8192       |
| transaction_prealloc_size       | 4096       |
+---------------------------------+------------+
33 rows in set (0.00 sec)

mysql> show variables like '%limit%';
+--------------------------+---------+
| Variable_name            | Value   |
+--------------------------+---------+
| delayed_insert_limit     | 100     |
| ft_query_expansion_limit | 20      |
| key_cache_division_limit | 100     |
| open_files_limit         | 10951   |
| query_cache_limit        | 1048576 |
| relay_log_space_limit    | 0       |
+--------------------------+---------+
6 rows in set (0.00 sec)




On Mon, Dec 15, 2008 at 12:24 PM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
> Mat Caughron wrote:
>>
>> Regarding query size:
>>
>> In general, is there an approved way to get the parser to indicate
>> average length of query size?
>
> You could do this with CSV logging and length() fairly easily.
>
> --Josh
>
>

In response to

Responses

sfpug by date

Next:From: Steve CrawfordDate: 2008-12-16 23:52:44
Subject: Re: IN question
Previous:From: Josh BerkusDate: 2008-12-15 21:25:52
Subject: Re: Reminder: party tommorrow, RSVP please

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group