On Mon, Sep 30, 2013 at 7:14 PM, akp geek wrote:
> Hi all -
>
> Currently we have set up one master one slave , which working
> fine. Now we need to replicate to an other slave. The problem we have ,
> the port that we use on primary can not be reached from the new slave. We
> can't t
Hi all -
Currently we have set up one master one slave , which working
fine. Now we need to replicate to an other slave. The problem we have ,
the port that we use on primary can not be reached from the new slave. We
can't the change the primary port also, because many applications usi
>
> you can control this with on error stop directive -- add it to your
> psqlrc if you want the setting to persist.
I hear what you're saying, but wonder about the implications:
It sounds like you can't trust your BEGIN to actually start a transaction
unless on_error_stop is set
The default fo
David Johnston writes:
> Moshe Jacobson wrote
>> Why does bool get special treatment?
>>
>> postgres# select 'abc', 1, false;
>> ?column? | ?column? | bool
>> --+--+--
>> abc |1 | f
>> (1 row)
> It doesn't (at least not as I see things in my client/version - note
Moshe Jacobson wrote
> Why does bool get special treatment?
>
> postgres# select 'abc', 1, false;
> ?column? | ?column? | bool
> --+--+--
> abc |1 | f
> (1 row)
It doesn't (at least not as I see things in my client/version - noted
below):
*SELECT 'abc'::text;*
On 09/30/2013 01:48 PM, Moshe Jacobson wrote:
Why does bool get special treatment?
|postgres# select 'abc', 1, false;
?column? | ?column? | bool
--+--+--
abc |1 | f
(1 row)|
Not always:
test=> select 'abc'::text, 1::int, 'f';
text | int4 | ?column?
-
Why does bool get special treatment?
postgres# select 'abc', 1, false;
?column? | ?column? | bool
--+--+--
abc |1 | f
(1 row)
Moshe Jacobson
Nead Werx, Inc. | Manager of Systems Engineering
2323 Cumberland Parkway, Suite 201 | Atlanta, GA 30339
mo...@neadwerx.co
On Mon, Sep 09/30/13, 2013 at 11:49:29AM -0400, Moshe Jacobson wrote:
> On Sun, Sep 29, 2013 at 2:18 AM, Ken Tanzer wrote:
>
> > After restarting the server in another window, I was surprised that my
> > command did not run in a transaction:
> >
> > spc_test_scratch=# BEGIN; DROP VIEW IF EXISTS p
On Mon, Sep 09/30/13, 2013 at 11:49:29AM -0400, Moshe Jacobson wrote:
> On Sun, Sep 29, 2013 at 2:18 AM, Ken Tanzer wrote:
>
> > After restarting the server in another window, I was surprised that my
> > command did not run in a transaction:
> >
> > spc_test_scratch=# BEGIN; DROP VIEW IF EXISTS p
On Mon, Sep 30, 2013 at 10:49 AM, Moshe Jacobson wrote:
>
> On Sun, Sep 29, 2013 at 2:18 AM, Ken Tanzer wrote:
>>
>> After restarting the server in another window, I was surprised that my
>> command did not run in a transaction:
>>
>> spc_test_scratch=# BEGIN; DROP VIEW IF EXISTS ptest_mip ; DROP
On Sun, Sep 29, 2013 at 2:18 AM, Ken Tanzer wrote:
> After restarting the server in another window, I was surprised that my
> command did not run in a transaction:
>
> spc_test_scratch=# BEGIN; DROP VIEW IF EXISTS ptest_mip ; DROP VIEW
> rent_info; \i create.view.rent_info.sql
> FATAL: terminati
Jayadevan M wrote:
> Thanks for the pointer. I do not really want to log the plans of queries,
> just the queries, execution
> time and a couple of other details (database,user). If I use the auto-explain
> module, it will end up
> printing the plan for all query execution in the log files?
You
12 matches
Mail list logo
