You do NOT need to call pg_free_result() on every result resource you create.
When result resources go out of scope, they are garbage collected just like everything else.
Unless you're hoarding your results somewhere, you can basically ignore this function.
Here's a little test you can run to confirm this: http://pastebin.com/ghw1PHuE
pg_free_result
(PHP 4 >= 4.2.0, PHP 5, PHP 7, PHP 8)
pg_free_result — Free result memory
Descrição
pg_free_result() frees the memory and data associated with the specified PgSql\Result instance.
This function need only be called if memory consumption during script execution is a problem. Otherwise, all result memory will be automatically freed when the script ends.
Nota:
This function used to be called pg_freeresult().
Parâmetros
-
result -
Uma instância de PgSql\Result, retornada por pg_query(), pg_query_params() ou pg_execute() (entre outras).
Valor Retornado
Retorna true em caso de sucesso ou false em caso de falha.
Registro de Alterações
| Versão | Descrição |
|---|---|
| 8.1.0 |
O parâmetro result agora espera uma instância de PgSql\Result;
anteriormente, um resource era esperado.
|
Exemplos
Exemplo #1 pg_free_result() example
<?php
$db = pg_connect("dbname=users user=me") || die();
$res = pg_query($db, "SELECT 1 UNION ALL SELECT 2");
$val = pg_fetch_result($res, 1, 0);
echo "First field in the second row is: ", $val, "\n";
pg_free_result($res);
?>O exemplo acima produzirá:
First field in the second row is: 2
Veja Também
- pg_query() - Execute a query
- pg_query_params() - Submits a command to the server and waits for the result, with the ability to pass parameters separately from the SQL command text
- pg_execute() - Sends a request to execute a prepared statement with given parameters, and waits for the result
add a note
User Contributed Notes 1 note
Stefan W ¶
11 years ago
