Although I, too, am not fond of the current command names, I'm not aware
of a naming conflict that is serious enough to warrant renaming. Do we
have even one example of one significant naming conflict?
Renaming executable seems likely to create much more confusion that it
will solve. I loathe th
At 3:50p -0400 on Sat, 29 Mar 2008, Tom Lane wrote:
>> Unable to connect to PostgreSQL server: private key file
>> "/var/www/.postgresql/postgresql.key" has wrong permissions
>
> The code appears to want 700 and ownership equal to that of the
> process executing libpq, ie, the apache server.
I ju
Message Digest
Volume 1 : Issue 8037 : "index" Format
Messages in this Issue:
200803/1458: Delete after trigger fixing the key of row numbers
200803/1459: Re: SELECT DISTINCT ON and ORDER BY
200803/1460: Re: SELECT DISTINCT ON and ORDER BY
200803/1461: Re: SELECT DISTINCT ON and ORDER BY
Message Digest
Volume 1 : Issue 8035 : "index" Format
Messages in this Issue:
200803/1421: Re: Survey: renaming/removing script binaries
(createdb, createuser...)
200803/1422: Re: Survey: renaming/removing script binaries (createdb,
createuser...)
200803/1423: Re: Using tables in other
Message Digest
Volume 1 : Issue 8036 : "index" Format
Messages in this Issue:
200803/1440: Re: Need help on how to backup a table
200803/1441: Persistent user-defined functions
200803/1442: Merge Joins and Views
200803/1443: Re: Persistent user-defined functions
200803/1444: PL/pgSQL Do
Message Digest
Volume 1 : Issue 8034 : "index" Format
Messages in this Issue:
200803/1400: Re: Survey: renaming/removing script binaries (createdb,
createuser...)
200803/1401: Re: Survey: renaming/removing script binaries (createdb,
createuser...)
200803/1402: Re: Survey: renaming/removin
Message Digest
Volume 1 : Issue 8031 : "index" Format
Messages in this Issue:
200803/1346: Re: RULES and QUALIFICATION for INSERT
200803/1347: Re: How to "use" database?
200803/1348: Re: RULES and QUALIFICATION for INSERT
200803/1349: Performance of update
200803/1350: Re: Performance o
Message Digest
Volume 1 : Issue 8032 : "index" Format
Messages in this Issue:
200803/1364: very delayed autovacuum on certain tables
200803/1365: Re: Survey: renaming/removing script binaries (createdb,
createuser...)
200803/1366: Re: Performance of update
200803/1367: Re: casting
Message Digest
Volume 1 : Issue 8030 : "index" Format
Messages in this Issue:
200803/1324: Re: casting from integer to boolean
200803/1325: Re: casting from integer to boolean
200803/1326: Re: casting from integer to boolean
200803/1327: Re: Survey: renaming/removing script binaries (cre
Message Digest
Volume 1 : Issue 8033 : "index" Format
Messages in this Issue:
200803/1382: Re: Using tables in other PostGreSQL database
200803/1383: Re: Survey: renaming/removing script binaries (createdb,
createuser...)
200803/1384: Re: Timezones in 8.2.7
200803/1385: Re: Timezo
On Mar 27, 8:28 am, [EMAIL PROTECTED] ("Albe Laurenz") wrote:
> sam wrote:
> > Iam trying to update a database table with approx 45000 rows. Iam not
> > updating all rows at a time. Iam updating 60 rows at a given time for
> > example. and this is happening in a FOR LOOP. A function that has the
>
Scott Marlowe wrote:
How do you do cross db access within a transaction?
You can't, and it's not likely that any code will be put in place to
do this.
But wasn't such code announced in 8.1? From
http://www.postgresql.org/about/news.422 :
"Two-Phase Commit (2PC): Long in demand for W
"Atkins-Trimnell, Angus Black" <[EMAIL PROTECTED]> writes:
> I have tried various owner/group/permissions combinations for
> WEB_HOME/.postgresql/postgresql.key. I have had it set as root:root with
> 700 permissions, postgresql:root with 700, and postgresql:postgresql with
> 700. I've also tried
"Harald Armin Massa" <[EMAIL PROTECTED]> writes:
> ... so I recommend updating the documentation to
> \du [PATTERN] list roles (users)
Done. I changed \dg the same way. psql's SGML docs seem okay already.
regards, tom lane
--
Sent via pgsql-general mailing list (pgs
Hello,
I am having trouble connecting to PostgreSQL 8.2 from an Apache2 web
server using certificates.
I have set up a CA on my server and used it to sign a certificate
(server.crt) created in a signing request based on a private key
(server.key), both of which reside in my PostgreSQL data direct
Olexandr Melnyk wrote:
> Hello,
>
> I'm interested in applying for this year's GSoC program, to work on
> PL/Mono: pluggable procedural language for PostgreSQL. The main
> purpose of the project is to allow programmers to write stored
> procedures for PostgreSQL database in one of the languages th
Sam Mason wrote:
Occasionally, though, I do have something where the DB-using app must
just submit a request to the DB and see if it works. Either the UI
doesn't have the privileges to run the same checks its self, or they're
just too expensive to do from the client (or to do twice). In those
Oh, I also know about 2pc, but that's not quite done yet, and it's not
perfect either. When it's working then maybe someone could work on
cross-db queries through it.
But I'm not looking for that, 2pc has so many more interesting
applications than cross db queries.
--
Sent via pgsql-general mai
Let me further explain things. From the perspective of PostgreSQL,
all transactions occur within a single instance of a connection to a
single database.
When that connection is lost, any transactions roll back.
Transactional integrity is therefore only guaranteed during the
duration of a connecti
x asasaxax wrote:
I have the following tablecreate table product(cod serial, user_cod
bigint, constraint product_fk Foreign Key(user_cod) references user(cod),
constraint product_pk Primary Key(cod, user_cod));
What i want to happend is that:
user_codcod
1
Olexandr Melnyk wrote:
Hello,
I'm interested in applying for this year's GSoC program, to work on PL/Mono:
pluggable procedural language for PostgreSQL. The main purpose of the
project is to allow programmers to write stored procedures for PostgreSQL
database in one of the languages that are sup
Chris Mayfield <[EMAIL PROTECTED]> writes:
>>> So the long and the short of it is that the COALESCE acts as an
>>> optimization fence in the presence of outer joins. We've seen this
>>> before and there are some rough ideas about fixing it.
> You may already have this rough idea somewhere, but it
Gregory Stark <[EMAIL PROTECTED]> writes:
> "Tom Lane" <[EMAIL PROTECTED]> writes:
>> Don't hold your breath though --- it'll take major planner surgery.
> In this case isn't all the planner needs the pathkey list to give it a hint
> that that ordering might be useful?
You could maybe make that w
On Thu, Mar 27, 2008 at 10:41:52PM -, Greg Sabino Mullane wrote:
>
> For the record, I think any renaming is a terrible idea, and a solution
> in search of a problem. Any change, no matter how long it takes, will
> break untold number of scripts, make us look bad, and frustrate
> people, simil
"Chris Mayfield" <[EMAIL PROTECTED]> writes:
> You may already have this rough idea somewhere, but it seems to me that the
> view could be flattened into the upper query as long as the join predicates
> don't depend on coalesced columns. In the examples I sent, even if the
> COALESCE is evaluated
Hello,
I'm interested in applying for this year's GSoC program, to work on PL/Mono:
pluggable procedural language for PostgreSQL. The main purpose of the
project is to allow programmers to write stored procedures for PostgreSQL
database in one of the languages that are supported by Mono platform
(
On Fri, Mar 28, 2008 at 8:44 PM, Brent Wood <[EMAIL PROTECTED]> wrote:
> I have mixed feelings,
>
> I agree that pretty much equivalent functionality CAN be delivered using
> schemas, but some RDBMS's do not have this restriction. Business cases &
> preferences do not necessarily follow database
Thank you very much Richard. It worked like a charm.
I Appreciate your help
Richard Huxton <[EMAIL PROTECTED]> wrote:
carty mc wrote:
> Thanks Richard, I went through dblink and tried it . But I am not
> able to pass variables to sql stmt of dblink_exec function .
> Basically If I hardcod
Joshua D. Drake wrote:
> I would note that system utilities can be renamed at the packagers
> behest.
>
> ./configure --exec-prefix=pg
>
> Yes this would create pgpg_ctl.
No, this would make configure abort with an error message.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.o
Steve Atkins wrote:
> What's the psql equivalent of the "standard" use case of "vacuumdb -a"?
There isn't a good one. A tool, possibly a psql option, to do "run this SQL
command in all databases", would allow us to get rid of clusterdb, reindexdb,
vacuumdb.
--
Sent via pgsql-general mailing l
Thank you for your prompt reply, I appreciate your insight on this.
> So the COALESCE has to be evaluated below the outer join, which means
> that the view can't be "flattened" into the upper query.
> ...
> So the long and the short of it is that the COALESCE acts as an
> optimization fence in th
"Tom Lane" <[EMAIL PROTECTED]> writes:
> In the case where you introduce the intermediate sub-select, the
> view *can* be flattened into that, producing
> SELECT id, COALESCE(opt, 0) AS opt FROM b ORDER BY id
> Again, that can't be flattened into the top query, but looking at
> it in isolati
carty mc wrote:
Thanks Richard, I went through dblink and tried it . But I am not
able to pass variables to sql stmt of dblink_exec function .
Basically If I hardcode the values for updating a table for the sql
statement in different database it is working fine. But What I wanted
to do is get the
33 matches
Mail list logo
