Re: [HACKERS] machine-readable pg_controldata?

Tom Lane wrote: > (FWIW, my recollection of the original design intention for > pg_controldata was that it was meant as a troubleshooting tool if the > database wouldn't start up. I'm somewhat bemused to hear that people > are trying to use it as part of production scripts. It wasn't meant to > p

Re: [HACKERS] Repetition of warning message while REVOKE

Stephen Frost writes: > * Tom Lane (t...@sss.pgh.pa.us) wrote: >> One thought is that the column cases should be phrased more like >> no privileges could be revoked for column "foo" of table "bar" > Looks like 'for column "foo" of relation "bar"' is more typical, so > that's what I did in the att

Re: [HACKERS] Explicit psqlrc

Peter Eisentraut writes: > I can see the environment variable variant as an analogy to BASH_ENV, > but what is the use case for the --psqlrc option? Wouldn't it be easier > and more useful to just be able to process more than one file, say by > specifying -f more than once? The analogy I was thi

Re: [HACKERS] SQL compatibility reminder: MySQL vs PostgreSQL

François Pérou wrote: My opinion is that PostgreSQL should accept any MySQL syntax and return warnings. I believe that we should access even innodb syntax and turn it immediately into PostgreSQL tables. This would allow people with no interest in SQL to migrate from MySQL to PostgreSQL without

Re: [HACKERS] Using GIN/Gist to search the "union" of two indexes?

Jesper Krogh writes: > select id from tablea,tableb where tablea.tableb_id = tableb.id and > tablea.text @@ to_tsquery('ftsquery') or tableb.text @@ > to_tsquery('ftsquery'); > > This one is doable .. using some "mocking" of queries in the > application. But if ftsquery is: > > "terma & termb" whe

Re: [HACKERS] SQL compatibility reminder: MySQL vs PostgreSQL

François Pérou wrote: I will continue using PostgreSQL and MySQL user base will continue to grow and one day it will be 1 PostgreSQL user for 1.000 MySQL users. This is life. People have a deep psychological addiction to their believes and ideas. IMHO, PostgreSQL has to be more flexible (in psy

Re: [HACKERS] SQL compatibility reminder: MySQL vs PostgreSQL

Le samedi 06 mars 2010 à 11:01 -0800, Josh Berkus a écrit : > However, "The server is free to return any value from the group" > doesn't > sound like the way we do things, ever. MySQL users might be OK with > queries which return an indeterminate answer; our users are not. > You'll > notice that S

Re: [HACKERS] SQL compatibility reminder: MySQL vs PostgreSQL

On 3/6/10 1:05 AM, Craig Ringer wrote: > Andrew Dunstan wrote: > >> But AIUI that won't be the same as the MySQL behaviour, as documented at >> : >> >>When using this feature, all rows in each group should have the same >>

Re: [HACKERS] Explicit psqlrc

On fre, 2010-03-05 at 11:30 +0100, Magnus Hagander wrote: > > Do you have a use-case where --psqlrc would be more useful than an > > environment variable, or is it *only* bike-shedding? ;) > > Just to be clear, the code difference isn't very large. Attached is a > patch that does both PSQLRC and -

Re: [HACKERS] C++ project using postgresql source

ok then ^^ thanks currently: rsync -avzCH --delete anoncvs.postgresql.org::pgsql-cvs . -- Regards, Kiswono P GB -- 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] C++ project using postgresql source

On lör, 2010-03-06 at 18:26 +0700, Kiswono Prayogo wrote: > Hi, good day everyone ^^ > i got these errors: primnodes.h:1155: error: expected unqualified-id > before ‘using’ > when i tried to compile plv8 project using g++, > > could postgresql use/chage variable name considering also C++ keywords?

[HACKERS] C++ project using postgresql source

Hi, good day everyone ^^ i got these errors: primnodes.h:1155: error: expected unqualified-id before ‘using’ when i tried to compile plv8 project using g++, could postgresql use/chage variable name considering also C++ keywords? that is: # using # typeid # typename # namespace # delete detailed e

Re: [HACKERS] SQL compatibility reminder: MySQL vs PostgreSQL

Andrew Dunstan wrote: > But AIUI that won't be the same as the MySQL behaviour, as documented at > : > >When using this feature, all rows in each group should have the same >values for the columns that are ommitted from