> On 27 Jun 2015, at 5:59, Robert Nikander wrote:
> In application code, prepared statements want to say: `select * from items
> where color_id = ?` and that `?` might be a int or null, so that doesn’t
> work.
You could add another parameter to test which expression to 'activate' in the
quer
hi, peoples!
Have a way to distribute connections for postgres master x master?
I need something... When i connect my apps, direct thia connections only
one IP, but this ip, automaticaly resolve one of my two masters servers
Example: app <---> ip 10.1.1.1
This 10.1.1.1 see my two masters in
Give a look to PEN, it is a load-balancing daemon :)
Luis Daniel Lucio Quiroz
CISSP, CISM, CISA
Linux, VoIP and much more fun
www.okay.com.mx
Need LCR? Check out LCR for FusionPBX with FreeSWITCH
Need Billing? Check out Billing for FusionPBX with FreeSWITCH
2015-06-27 9:32 GMT-04:00 Gerdan Rezen
Hi Dave:
On Fri, Jun 26, 2015 at 2:59 AM, Dave Johansen wrote:
> It appears that calling "SELECT insert_test_no_dup('2015-01-01', 1, 1)"
> cause the XID to increment? I'm not sure if it's only when the exception
> happens or all the time, but if there some way to prevent the increment of
> XID b
To make a long story short, few years ago I was complaining that the sort order
of varchar, in UTF-8, was ignoring blanks, that is that the sort order was:
a
a
A
A
à
b
B
But, i was in need of a sort order that would place blanks BEFORE the other
char, that is I wou
I'm running this SQL statement:
insert into Favorite (patronId, titleId)
select 123, 234
where not exists (
select 1 from Favorite where patronId = 123 and titleId = 234
)
It normally runs perfectly, but will rarely fail and I just can't see
any way that it could. :-|
The exception I get is th
2015-06-28 6:37 GMT+02:00 Larry Meadors :
> I'm running this SQL statement:
>
> insert into Favorite (patronId, titleId)
> select 123, 234
> where not exists (
> select 1 from Favorite where patronId = 123 and titleId = 234
> )
>
> It normally runs perfectly, but will rarely fail and I just can'
On Sat, Jun 27, 2015 at 9:47 PM, Pavel Stehule wrote:
> you can protect it against this issue with locking - in this case you can
> try "for update" clause
>
> http://www.postgresql.org/docs/9.4/static/explicit-locking.html
>
> insert into Favorite (patronId, titleId)
> select 123, 234
> where not
2015-06-28 6:52 GMT+02:00 Peter Geoghegan :
> On Sat, Jun 27, 2015 at 9:47 PM, Pavel Stehule
> wrote:
> > you can protect it against this issue with locking - in this case you can
> > try "for update" clause
> >
> > http://www.postgresql.org/docs/9.4/static/explicit-locking.html
> >
> > insert in
