Alvaro Herrera [EMAIL PROTECTED] writes:
No, that's why I haven't mentioned it :-) I know I can't do anything
about objects in other databases. But I have wondered if we could
implement CASCADE behavior for an object whose dependencies are only
local to the current database (where CASCADE
--- Devrim GUNDUZ [EMAIL PROTECTED] wrote:
Could you please tell us why integer datetimes
should be enabled in our
RPMs by default?
We are not sure that many people need it, also it's
easy for someone to
add this support using the SRPMs provided.
Consistent precision through the range
In postgresql 8.0, create table as ... statements
appear not to logged unless log_statement = 'all' in
postgresql.conf. We are trying to reduce noise in the
logs from pgAdminIII and phpPgAdmin, but we use a lot
of 'create table as ...' queries that need to be
logged, and their duration tracked.
Thomas F.O'Connell wrote:
I put together a little Perl script (which assumes proper installation
of both DBI and DBD::Pg and that template1 exists) that takes care of
the character conversion vulnerability:
dont hardcode pgsql superuser :)
Toma
---(end of
S Murthy Kambhampaty [EMAIL PROTECTED] writes:
Consistent precision through the range of allowed
values sceems a feature worth having.
I wonder why you are not sure that many people need
it.
Because almost nobody has complained about the lack of it.
(I'm talking about actual field experience
--- Tom Lane [EMAIL PROTECTED] wrote:
Because almost nobody has complained about the lack
of it.
(I'm talking about actual field experience of there
being a
problem, not somebody objecting that it sounds like
a
feature worth having.)
It should also be pointed out that we are still
