On Tue, 2013-07-09 at 10:45 +0200, Andreas Joseph Krogh wrote:
> I would expect the queries above to return FALSE and have to use
> INFINITY to have them return TRUE. I don't understand what you mean by
> ranges not allowing either bound to be NULL as it seems to be the case
> (as in "it works").
Andreas Kretschmer writes:
> '3 years' != '2 years 11 mons 30 days', but i got 0 rows, why?
Well, actually:
regression=# select '3 years'::interval = '2 years 11 mons 30 days'::interval;
?column?
--
t
(1 row)
IIRC, interval comparison operators normalize the two values assuming that
On 8/29/13, Michael Nolan wrote:
> On 8/29/13, Andreas Kretschmer wrote:
>
>> I'm using 9.2.4.
>
>
> What is the content of the field 'birthday''? My guess is there's a
> null value for the field, in which case you are comparing two nulls.
Oops, missed seeing the first half of the post with the
John R Pierce wrote:
> On 8/27/2013 6:49 PM, 高健 wrote:
>> For a query and insert action,
>> Firstly , the data is pull into private memory of the backend
>> process which is service client.
> if you're just writing this data into another table, why not do
> it all in SQL ?
>
> INSERT INTO
On 8/29/13, Andreas Kretschmer wrote:
> is there a bug in age()?
>
> test=*# select *, age(birthday), age (current_date-1, birthday) from
> birthday ;
> id | birthday | age | age
> ++-+-
> 1 | 2010-08-29 | 3 years | 2 years 11 mons
On 08/29/2013 01:11 PM, Andreas Kretschmer wrote:
is there a bug in age()?
test=*# select *, age(birthday), age (current_date-1, birthday) from birthday ;
id | birthday | age | age
++-+-
1 | 2010-08-29 | 3 years | 2 years 11 mo
On Thu, Aug 29, 2013 at 09:11:07PM +0200, Andreas Kretschmer wrote:
> test=*# select * from birthday where age(birthday) != age (current_date-1,
> birthday);
> id | birthday
> +--
> (0 rows)
>
> '3 years' != '2 years 11 mons 30 days', but i got 0 rows, why?
What does
selec
is there a bug in age()?
test=*# select *, age(birthday), age (current_date-1, birthday) from birthday ;
id | birthday | age | age
++-+-
1 | 2010-08-29 | 3 years | 2 years 11 mons 30 days
(1 row)
Time: 0,322 ms
test=*# select * fr
"Nicholson, Brad (Toronto, ON, CA)" writes:
> I'm seeing something odd in my DB stats. This is PG 9.2.4 on CentOS. I know
> the stats collector can be off at times, but I am curious as to why it would
> be off in such a case. I know that under heavy load the stats collector can
> be off some
Hi,
I'm seeing something odd in my DB stats. This is PG 9.2.4 on CentOS. I know
the stats collector can be off at times, but I am curious as to why it would be
off in such a case. I know that under heavy load the stats collector can be
off sometimes, but this system was barely doing anything
Hello.
At work we have a program that seems to be stressing the SSI
implementation, and I thought that it could provide useful insights to
better tune it. In particular, there are a few parts that are
described as "chosen entirely arbitrarily (and without benchmarking)",
and we may provide some of
So sorry for this inconvenience, please delete the same one i've posted.
This is the first time i'm posted to this maillist.
On 2013/08/29, at 23:06, Bocap wrote:
> Hi all,
>
> I think it is not documented the follow using of replication, but is that
> correct.
>
> 1. Instead of using pg_bas
Hi all,
I think it is not documented the follow using of replication, but is that
correct.
1. Instead of using pg_basebackup for standby DB, i initdb for both standby and
primary.
2. Create recovery.conf in standby DB, and start both nodes.
Now it work fine for me, but is it sure that no probl
Hi all,
I think it is not documented the follow using of replication, but is that
correct.
1. Instead of using pg_basebackup for standby DB, i initdb for both standby and
primary.
2. Create recovery.conf in standby DB, and start both nodes.
Now it work fine for me, but is it sure that no probl
Hi,
For finding duplicates you can use ctid.
select o.ctid, o.a, o.b from test o
where exists ( select 'x'
from test i
where i.a = o.a
and i.b = o.b
and i.ctid < o.ctid
);
for deleting,
delete from test
where
Hi all,
Is there any way to delete duplicate rows in psql with no unique fields? I
have a set of old records with their duplicates in my db and they are all
having the same fields. How can I delete duplicates? Thanks in Advance,Arun
I have a question about hot_standby_feedback parameter. In my
understanding, if this parameter is on, a long running transaction on
standby will not be canceled even if the transaction conflicts.
So I have primary PostgreSQL and standby PostgreSQL running 9.2.4.
On primary:
create table t1(i int)
17 matches
Mail list logo
