[HACKERS] Invitation to the OSGEO Code Sprint 2016 / Feb 23-26 in Paris
Hi everyone, The Open Source Geospatial Foundation is organizing its annual Code Sprint this year in Paris from February 23 to February 26. Many PostGIS developers will attend this event, including Paul Ramsey, Olivier Courtin, and others... This a great opportunity to work with them on how to improve PostgreSQL in this field. The Code Sprint will be hosted by the Mozilla Foundation ( 16bis Boulevard Montmartre, 75009 Paris ). Dalibo's office is right across the street and we'll be a sponsor for this event, so if you're interested in attending this event don't hesitate to contact us, we're happy to help. You'll find more information on the wiki page: https://wiki.osgeo.org/wiki/Paris_Code_Sprint_2016 See you in Paris next month :) -- Damien Clochard -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
[HACKERS] PG Session #2 : Call For Papers
Hi,
The first PostgreSQL Session organized by Dalibo last february was
a big success. More than 80 public and private participants gathered in
Paris.
Dalibo and Oslandia want to carry on this success and set up a
new conference day dedicated to PostGIS, on June 23d in Paris.
http://www.postgresql-sessions.org/en/2/
The call for paper for this second session is now open. Here is some
expected topics (non-exhaustive list) :
* Feedback on information systems architectures using PostGIS in
specific contexts ("exotic" constraints, high volumes…)
* decision process of GIS database
* migration from another spatial DB
* PostGIS 2.0 new features, WKT Raster
* Interoperability between PostGIS 2.0 and other softwares
* Link between PostgreSQL and PostGIS, and planned evolution
* etc.
Talks duration will be 45', including a 15' questions and answers session.
Thank you for sending the following elements at contact@postgresql-
sessions.org before april 22d :
* Presentation title
* Name of speaker(s)
* Summary of presentation (100-250 words)
For any question, do not hesitate to contact us :
cont...@postgresql-sessions.org.
If you have any friends or colleagues that you think would be interested
in giving a talk, please forward this message to them!
PS : Slides from the first PG Session are available at :
http://www.postgresql-sessions.org/en/1/
--
damien clochard
dalibo.com | dalibo.org
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] List traffic
Le 11/05/2010 19:24, Alvaro Herrera a écrit : > Excerpts from Marc G. Fournier's message of mar may 11 09:58:34 -0400 2010: > >> If list traffic, especially on -hackers, is getting so large, should we >> look at maybe splitting it? I could easily enough split things such that >> I duplicate the subscriber list, so nobody would have to subscribe, but it >> would make it easier for ppl to filter their incoming ... ? > > Maybe we could create a separate list where people would send patches, > and keep patchless discussion on -hackers? > > Just a thought ;-) Here's a simple description of how i use and see the -hackers list. I'm what you could call a "silent reader", like many other subscribers i don't participate to the discussions but i'm happy to be able to follow them. I'm not an end-user and i'm not a developper. Just a guy that wants to follow the "making-of" this project. Sure the traffic is huge and sometimes i have thousands of unread messages. But somewhat i managed to follow the threads i'm interested in and leave asides others... If this list is split in two smaller ones, then i guess i'll follow both and it won't help me in any way. I guess it would even make things more difficult to understand. This is my modest experience. Clearly things can be improved, but speaking for myself i don't think that splitting the list is a good idea. -- damien clochard http://www.dalibo.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] Have \d show child tables that inherit from the specified parent
Greg Sabino Mullane wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
This one is very basic, it just shows the child tables of a specific
table when you type \d in psql :
I'm not so jazzed about this, as I work on systems that have literally
hundreds of child tables.
hi everyone.
Thanks for your comments.
I must admit that i didn't asked myself much questions when i
implemented that feature. As i said i picked that item almost randomly
in the todo list. I choosed to show child table on \d instead \d+ in
order to be consistant with the fact that \d shows the mother of the
specified table.
That being said i recognize that people who have dozens of child tables
might get annoyed by this patch.
Here's 3 ideas that could make things better :
1- When using \d , only show the numbers of child tables
2- Only display the list of child table when \d+ is used. (mode ???)
3- Display the child table names in line, instead of one line per table.
Here's what it would look like :
# \d mother
Table "public.mother"
Column | Type | Modifiers
+-+-
id | integer | not null default nextval('mother_id_seq'::regclass)
This table has 5 child tables. Use \d+ to display them.
#\d+ mother
Table "public.mother"
Column | Type | Modifiers
+-+-
id | integer | not null default nextval('mother_id_seq'::regclass)
Child tables : daughter1, daughter2, daughter3, daughter4, daughter5
Does it look better ?
--
damien clochard
dalibo.org | dalibo.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
[HACKERS] Have \d show child tables that inherit from the specified parent
Hello,
Last week, i took some time to check if i was still able to write some
basic C code. So i looked into the TODO list and picked some trivial items.
This one is very basic, it just shows the child tables of a specific
table when you type \d in psql :
# create table mother(id SERIAL);
# create table daughter() inherits(mother);
# create table daughter2() inherits(mother);
# create schema plop;
# create table plop.daughter3() inherits(mother);
# \d mother
Table "public.mother"
Column | Type | Modifiers
+-+-
id | integer | not null default nextval('mother_id_seq'::regclass)
Child tables: daughter,
daughter2,
plop.daughter3
I understand that it may not be the best moment to submit such a trivial
patch, as most of you are working hard on more important topics. If you
think i should submit it later, just let me know.
BTW, this is the first patch i submit so any comment is more than welcome.
Regards,
--
damien clochard
dalibo.com | dalibo.org
? logfile
? psql
Index: describe.c
===
RCS file: /projects/cvsroot/pgsql/src/bin/psql/describe.c,v
retrieving revision 1.199
diff -c -r1.199 describe.c
*** describe.c 11 Feb 2009 19:12:04 - 1.199
--- describe.c 25 Feb 2009 22:53:50 -
***
*** 1668,1673
--- 1668,1699
}
PQclear(result);
+ /* print child tables */
+ printfPQExpBuffer(&buf, "SELECT c.oid::pg_catalog.regclass FROM pg_catalog.pg_class c, pg_catalog.pg_inherits i WHERE c.oid=i.inhrelid AND i.inhparent = '%s' ORDER BY i.inhseqno;", oid);
+
+ result = PSQLexec(buf.data, false);
+ if (!result)
+ goto error_return;
+ else
+ tuples = PQntuples(result);
+
+ for (i = 0; i < tuples; i++)
+ {
+ const char *s = _("Child tables");
+
+ if (i == 0)
+ printfPQExpBuffer(&buf, "%s: %s", s, PQgetvalue(result, i, 0));
+ else
+ printfPQExpBuffer(&buf, "%*s %s", (int) strlen(s), "", PQgetvalue(result, i, 0));
+ if (i < tuples - 1)
+ appendPQExpBuffer(&buf, ",");
+
+ printTableAddFooter(&cont, buf.data);
+ }
+ PQclear(result);
+
+
+
if (verbose)
{
const char *s = _("Has OIDs");
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
