Greg Sabino Mullane escreveu:
>
>> * Child tables are sorted by name
>> * \d only shows the number of child tables
>> * \d+ shows the full list
>
>> This table has 4 child table(s). Use \d+ to display them.
>
> Would be nice if you could get rid of that ugly '(s)' part.
>
What about "Child Tabl
Robert Haas wrote:
> 2009/4/21 KaiGai Kohei :
>> Robert, currently I could not find semantics breaks in your suggestion.
>> I plan to update SE- implementation to skip checks during foreign-key
>> constraints and add a new SE- permission: "reference" which allows
>> to set up fereign-keys.
>
> Sou
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
> * Child tables are sorted by name
> * \d only shows the number of child tables
> * \d+ shows the full list
> This table has 4 child table(s). Use \d+ to display them.
Would be nice if you could get rid of that ugly '(s)' part.
> Child table
A couple months back I wrote:
> "Eric Thompson" writes:
>> [ http://archives.postgresql.org//pgsql-bugs/2009-03/msg00116.php ]
> Hmm. Tracing through this, it seems your child tables have exactly 101
> separate constraint clauses; removing one from the parent table gets it
> down to 100. Which
I will write separated mail about rollup.
Can you send me some links or information about "CTE"? What is it?
Also, I need some deep knownledge about postgresql aggregation
calculation (executor part) - can you help me (links, books, name of
source files, etc)?.
After get additional information i wi
2009/5/10 Олег Царев :
> Hello, Pavel.
>
> I read you letter, and found some points:
>
> a) Simple transformation any GROUPING SETS in GROUP BY + UNION ALL
> require clone source for every group.
> It's so slow.
> My point: we can make for start simple implementation.
> b) Your sollution it's so go
On Sun, May 10, 2009 at 4:07 PM, Tom Lane wrote:
> This might or might not be worth doing, but it seems pretty nearly
> entirely useless for the claimed purpose. What is your division between
> "user errors" and "system errors", and how will the SQLSTATE help you
> make that?
We use http://www.p
Guillaume Smet writes:
> A customer of us recently wanted to separate user errors from system
> errors as different teams are working on these 2 types of errors and
> while they might want to ignore user errors (bad-written SQL queries
> and so on), they want to be sure system errors are analyzed
Guillaume Smet wrote:
On Sun, May 10, 2009 at 3:29 PM, Andrew Dunstan wrote:
If we're going to do this I think it needs to be added to CSV log output
too.
AFAICS, it's already done for the CSV output hence my "the only way to
have the SQL state in the *standard* log file".
Did I mi
Hello, Pavel.
I read you letter, and found some points:
a) Simple transformation any GROUPING SETS in GROUP BY + UNION ALL
require clone source for every group.
It's so slow.
My point: we can make for start simple implementation.
b) Your sollution it's so good, IMHO
WITH q AS (SELECT * FROM some)
On Sun, May 10, 2009 at 3:29 PM, Andrew Dunstan wrote:
> If we're going to do this I think it needs to be added to CSV log output
> too.
AFAICS, it's already done for the CSV output hence my "the only way to
have the SQL state in the *standard* log file".
Did I miss something?
Thanks for your f
Guillaume Smet wrote:
Hi -hackers,
A customer of us recently wanted to separate user errors from system
errors as different teams are working on these 2 types of errors and
while they might want to ignore user errors (bad-written SQL queries
and so on), they want to be sure system errors are a
Hello
some other info is on http://wiki.postgresql.org/wiki/Grouping_Sets
Maybe in e few weak I'll have some a prototype based on CTE. My older
technique based on hashed tables should be well, but it carry lot of
unshared code. Using CTE means so we can optimize CTE and GROUPING
SETS together. I
Hello all.
Please, approve my ideas for implementation.
Standart has feature T431: Extended grouping capabilities.
This feature i found in TODO-list:
http://wiki.postgresql.org/wiki/Todo -> SQL Commands -> TO DO
MS SQL 2005 partial support this feature:
http://www.kodyaz.com/articles/sql-server-2
On Sun, May 10, 2009 at 2:32 PM, Guillaume Smet
wrote:
> I attached a patch which allows to add the SQL state code into the
> log_line_prefix. I used %e (as in error) as %s is already used.
Patch added to the next commit fest page.
--
Guillaume
--
Sent via pgsql-hackers mailing list (pgsql-ha
Hi -hackers,
A customer of us recently wanted to separate user errors from system
errors as different teams are working on these 2 types of errors and
while they might want to ignore user errors (bad-written SQL queries
and so on), they want to be sure system errors are analyzed carefully.
A good
16 matches
Mail list logo
