Re: psql setenv command

Поиск
Список
Период
Сортировка
От Josh Kupershmidt
Тема Re: psql setenv command
Дата
Msg-id CAK3UJRHT-+OtunBxm+6m1WH4Fn-HXqsLQE-cfiRM1mrYeeVaYg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: psql setenv command  (Andrew Dunstan <andrew@dunslane.net>)
Ответы Re: psql setenv command  (Andrew Dunstan <andrew@dunslane.net>)
Список pgsql-hackers
On Sat, Nov 26, 2011 at 11:02 AM, Andrew Dunstan <andrew@dunslane.net> wrote:
>> Also, should the malloc() of newval just use pg_malloc() instead?
>
> Yes, also done.

This bit is unnecessary, since pg_malloc() takes care of the error handling:

+            if (!newval)
+            {
+                psql_error("out of memory\n");
+                exit(EXIT_FAILURE);
+            }


Also, the help output for setenv bleeds over an 80-character terminal,
and it seems the rest of the help outputs try to stay under this
limit. And an OCD nitpick: most of the psql-ref.sgml examples show
'testdb' at the prompt, how about we follow along.

 Other than those small gripes, the patch looks fine. Attached is an
updated version to save you some keystrokes.

Josh

Вложения

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: Patch: add timing of buffer I/O requests
Следующее
От: Bruce Momjian
Дата:
Сообщение: Allow pg_dumpall to use dumpmem.c functions, simplify exit code