Re: proposal: multiple psql option -c

Поиск
Список
Период
Сортировка
От Pavel Stehule
Тема Re: proposal: multiple psql option -c
Дата
Msg-id CAFj8pRA6gHwxGchYdh4zKqfUbp=N-406M_jXAS7tu6PHBA3gjQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: proposal: multiple psql option -c  (Robert Haas <robertmhaas@gmail.com>)
Ответы proposal: multiple psql option -c  ("David G. Johnston" <david.g.johnston@gmail.com>)
Список pgsql-hackers


2015-07-23 17:52 GMT+02:00 Robert Haas <robertmhaas@gmail.com>:
On Fri, Jul 17, 2015 at 12:36 AM, Pavel Stehule <pavel.stehule@gmail.com> wrote:
>> Or just properly understand the ; ?
>>
>> -c "select * from foo; update bar set baz = 'bing'; vacuum bar;"
>
> there is a risk of compatibility issues - all statements runs under one
> transaction implicitly

So what?

[pavel@dhcppc2 ~]$ psql -c "insert into x values(txid_current()::text);insert into x values(txid_current()::text)" postgres
INSERT 0 1
[pavel@dhcppc2 ~]$ psql postgres -c "select * from x"
  a  
------
 1888
 1888
(2 rows)

I would to run -c command in separate transactions (when option --single-transaction is not used).

Then is possible run

-c "select pg_reset ...()" -c "vacuum analyze ..."

Regards

Pavel

p.s.

the state string "INSERT 0 1" is buggy probably

 

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

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

Предыдущее
От: Simon Riggs
Дата:
Сообщение: Re: MultiXact member wraparound protections are now enabled
Следующее
От: "David G. Johnston"
Дата:
Сообщение: proposal: multiple psql option -c