On Wed, Feb 9, 2011 at 10:17, Andrew Dunstan wrote:
> Isn't this all really a bug fix that should be backpatched, rather than a
> commitfest item?
Sure, but we don't have any bug trackers...
--
Itagaki Takahiro
--
Sent via pgsql-general mailing list (pgsql-general@postgre
a check
> for either kind of infinity and return an error if that's the case? I
Maybe so. It also works if we had infinity on timestamp overflow, but
I've not tested yet. Anyway, we need similar fix for timestamp versions.
--
Itagaki Takahiro
--
Sent via pgsql-general mailing list (pgs
;infinity', '1
sec') AS a(x);
=# SELECT x FROM generate_series('infinity'::timestamptz, 'infinity',
'1 sec') AS a(x);
> postgres=# SELECT x FROM generate_series(1, 9,-1) AS a(x);
> postgres=# SELECT x FROM generate_series(1, 9,3) AS a(x);
They work as expe
, replication
or snapshot management requires special skills to review.
I'm worrying about new reviewers hesitate to review a patch that has
a previous reviewer, and then, if they think the remaining patches are
too difficult for them, they would just leave the commitfest page.
--
Itagaki Takahi
any plans for it? According to the commitfest app, one patch
has only one reviewer at once. A new reviewer might avoid reviewing
a patch that have another reviewer already.
--
Itagaki Takahiro
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your su
;, "Local Settings" or direct child of %USERPROFILE%,
but anyway some of them would be better than "Program Files".
Regards,
---
ITAGAKI Takahiro
NTT Open Source Software Center
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
violations.
Please use pgloader (http://pgfoundry.org/projects/pgloader/)
for the purpose.
Regards,
---
ITAGAKI Takahiro
NTT Open Source Software Center
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
se a better way:
EXECUTE 'INSERT INTO ' || ctable || ' VALUES( ($1).* )' USING new;
Regards,
---
ITAGAKI Takahiro
NTT Open Source Software Center
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Tom Lane <[EMAIL PROTECTED]> wrote:
> ITAGAKI Takahiro <[EMAIL PROTECTED]> writes:
> > I found that the planner can deduce equality operators,
> > but cannot deduce inequality ones.
> > Are there any plans to improve handling of them?
>
> Not particular
Index Cond: (i < 100)
>-> Index Scan using u_pkey on u (cost=0.00..9.94 rows=96 width=4)
> Index Cond: (i < 100)
Regards,
---
ITAGAKI Takahiro
NTT Open Source Software Center
---(end of broadcast)---
TIP 1: if posting/
-
Nested Loop (cost=0.00..337.42 rows=1 width=8)
-> Index Scan using u_pkey on u (cost=0.00..9.94 rows=96 width=4)
Index Cond: (i < 100)
-> Index Scan using t_pkey on t (cost=0.00..3.40 rows=1 width=4)
11 matches
Mail list logo