x27;re so used to thinking of 'Yes' as
representing a text value, when Postgres doesn't see it that way.
Perhaps if it was "Select text", and even "Select int<42>" it would
be more obvious that "Select " or "Select <42>" required type
inference.
But that's just dreaming...
Regards,
--
Rowan Collins
[IMSoP]
[1]
http://www.postgresql.org/message-id/200806171229.m5HCTfsI091593%40wwwmaster.postgresql.org
[2] http://www.postgresql.org/message-id/19666.1213709303%40sss.pgh.pa.us
Regards,
--
Rowan Collins
[IMSoP]
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
it can connect properly to the postgres
server on port 5432
It sounds like (b) is currently the issue.
--
Rowan Collins
[IMSoP]
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
est_z
FROM
xyzzy
GROUP BY
x
I find this a lot easier to understand than window functions; I've no
idea how its performance compares.
--
Rowan Collins
[IMSoP]
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www
you need" parameter.
Personally, I'm definitely in the "this is surprising behaviour" camp,
although "surprising" and "wrong" aren't *necessarily* the same thing,
so I'll leave it to greater minds to decide on the latter...
--
Rowan Collins
[IMSoP]
he function for
every row in some_huge_table? Or should it run at most 10 times?
Which is desired would depend on the situation, but there's no real way
to indicate in the syntax.
--
Rowan Collins
[IMSoP]
sically
like a set of form controls, a well-thought-out web app can look and
feel much the same as a well-thought-out Windows app.
I do still think native GUI apps, and maybe even some script-oriented
ones, have their place, but with the right toolkit, it's not necessarily
cut and dr
that
Postgres doesn't know (or care) which where clause is "additional". The
only "original" result set is the one with no where clause at all, which
contains rows for 'pg_statistics' etc.
--
Rowan Collins
[IMSoP]
--
Sent via pgsql-general mailing list (pgsql-ge
On 08/10/2013 23:03, Rowan Collins wrote:
With tables_with_dates As (
select table_name, to_date(right(table_name, 8), 'MMDD') blah
from information_schema.tables
where table_schema = ''
and table_catalog = ''
)
Select table_name, blah
W
e(right(table_name, 8), 'MMDD') blah
from information_schema.tables
where table_schema = ''
and table_catalog = ''
)
Select table_name, blah
Where blah > '2013-01-01'::date
--
Rowan Collins
[IMSoP]
the database end. If database
security is a concern, you could have a login with extremely limitied
privileges, and whitelist it explicitly in pg_hba.conf for this purpose.
Regards,
--
Rowan Collins
[IMSoP]
OPY
command. This may or may not matter, depending on setup - for instance,
you might trust local Unix sockets, meaning someone would need access to
the box first. It's probably best to never have a non-interactive
process able to connect with elevated privileges though.
--
Rowan Collin
ilar views) is that the query is waiting on some
kind of lock, rather than just executing slowly.
Regards,
--
Rowan Collins
[IMSoP]
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
it should probably either be considered a
parser bug, or listed as a restriction on operator creation alongside --
and /* (or both).
Regards,
--
Rowan Collins
[IMSoP]
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
, you can just concentrate on the single task you need to work.
This will probably seem less good an idea if you need to retrieve data
from the stored proc, or if there's a possibility of more complex
linkages being needed later anyway.
--
Rowan Collins
[IMSoP]
--
Sent via pgsql-gener
On 29/04/2013 17:04, Shaun Thomas wrote:
> On 04/26/2013 09:39 AM, Rowan Collins wrote:
>> If I run "ANALYZE temp_fares_mappings;" - the table which is being
>> Updated, and is the outermost in the query plan - the problem goes
>> away *even though the Query Plan
nux-gnu-gcc (Gentoo Hardened 4.5.4 p1.0, pie-0.4.7) 4.5.4,
64-bit"
Does anyone have any idea what's going on here, and whether it is in
fact a bug? It certainly feels like one...
Thanks for your time.
--
Rowan Collins
S
nux-gnu-gcc (Gentoo Hardened 4.5.4 p1.0, pie-0.4.7) 4.5.4,
64-bit"
Does anyone have any idea what's going on here, and whether it is in
fact a bug? It certainly feels like one...
Thanks for your time.
--
Rowan Collins
[IMSoP]
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
18 matches
Mail list logo
