* 高健 (luckyjack...@gmail.com) wrote:
> Is there any common calculation methods for deciding the max_connections
> value?
max_connections is a hard limit and so you'd want to have that higher
than the number of connections you actually expect to have. The general
recommendation is to have the same
Thanks a lot!
I have understand this now.
And the following:
>In general you only want to have as many actual connections to PG
>as you have CPU cores in your database server.
This made me consider the appropriate value for max_conennections.
This might be another topic I think.
I am wo
* 高健 (luckyjack...@gmail.com) wrote:
> So I can draw a conclusion:
>
> Prepared statement is only for use in the same session at which it has
> been executed.
Prepared statements are session-local.
> It can not be shared via multiple sessions.
Correct.
> That is, when in some special situati
高健 wrote:
> Prepared statement is only for use in the same session at which it has been
> executed.
> It can not be shared via multiple sessions.
That is correct, see
http://www.postgresql.org/docs/current/static/sql-prepare.html
> That is, when in some special situations ,
> if I have to use
Hello everybody:
Sorry for disturbing.
I experience the prepared statement of postgresql via psql and have one
question:
In terminal A:
I prepared:
postgres=# prepare test(int) AS
postgres-# select * from customers c where c.cust_id = $*1*;
PREPARE
postgres=#
Then run:
postgres=# e
