thanks very much
specialy for Peter
Eisentraut
On Fri, May 08, 2009 at 04:43:44PM -0400, Alvaro Herrera wrote:
Ricardo Bessa escribió:
Hi,
I think that can be useful the command \di on psql show the method of
index (hash, btree, ...) like:
test=# \di
List of relations
Schema | Name
David Fetter da...@fetter.org writes:
On Fri, May 08, 2009 at 04:43:44PM -0400, Alvaro Herrera wrote:
One gripe I had with \d and indexes the other day is that it sucks
on functional indexes -- it just says pg_expression_1.
Any ideas for a better naming convention?
Changing the naming
Hi,
Le 8 mai 09 à 23:50, Tom Lane a écrit :
mmm ... I've recently been forced into using git for another project,
and I find myself mystified as to why anyone would want to use it.
Seems like baroqueness and unexpected behaviors are all over the
thing.
As a user of darcs I've been reacting
Tom Lane escribió:
David Fetter da...@fetter.org writes:
On Fri, May 08, 2009 at 04:43:44PM -0400, Alvaro Herrera wrote:
One gripe I had with \d and indexes the other day is that it sucks
on functional indexes -- it just says pg_expression_1.
Any ideas for a better naming convention?
On Fri, May 08, 2009 at 09:04:18PM -0400, Andrew Dunstan wrote:
Joshua D. Drake wrote:
Hello,
Here is a diff of version_stamp.pl. It is not quite done as I can't
actually get it to run. No matter what I do it doesn't appear to be able
to open configure.in.
If someone could help me figure
I wrote:
... So it appears to me that instead of taking an average-case correction
as is done in this patch and the old coding, we have to explicitly model
the matched-tuple and unmatched-tuple cases separately.
I've applied the attached patch that does things this way. I did not do
anything
Erik Rijkers wrote:
2009.05.09
pg_migrator alpha 5 results
from PostgreSQL 8.3.7 to 8.4cvs
Centos 5.2 x86_64 GNU/Linux
pg_migrator ran without errors.
Of 120 tables, all smaller tables
have the correct rowcount, but all
larger tables are 'truncated' at
around 10 million rows. I
Hi,
Here's a second version. Main changes are :
* Child tables are sorted by name
* \d only shows the number of child tables
* \d+ shows the full list
Which gives :
postgres=# \d mother
Table public.mother
Column | Type | Modifiers
On Sun, May 10, 2009 02:05, Alvaro Herrera wrote:
Erik Rijkers wrote:
2009.05.09
pg_migrator alpha 5 results
from PostgreSQL 8.3.7 to 8.4cvs
Centos 5.2 x86_64 GNU/Linux
pg_migrator ran without errors.
Of 120 tables, all smaller tables
have the correct rowcount, but all
larger tables
On Sat, May 9, 2009 at 7:00 PM, Tom Lane t...@sss.pgh.pa.us wrote:
I wrote:
... So it appears to me that instead of taking an average-case correction
as is done in this patch and the old coding, we have to explicitly model
the matched-tuple and unmatched-tuple cases separately.
I've applied
Erik Rijkers e...@xs4all.nl writes:
On Sun, May 10, 2009 02:05, Alvaro Herrera wrote:
I'm wondering that it could have forgotten to migrate the later table
segments ...
It seems al 'truncated' tables give
pg_relation_size(oid) = 1073741824
Looks like Alvaro nailed it. Bruce, you reading?
On Sun, May 10, 2009 at 3:59 AM, Alvaro Herrera
alvhe...@commandprompt.com wrote:
Yeah. (I note that the expressions are already shown as footers when
you display the table instead of the index. It seems like the \d code
for indexes did not get updated when that new code was added.)
Made
Updated with an additional line in the comments for get_indexdef
* if colno == -999, we only want the name of the variables that
make up the index
Apologies for leaving this out in my earlier post.
Regards,
Khee Chin.
index.patch
Description: Binary data
--
Sent via pgsql-hackers
14 matches
Mail list logo
