OK, I found the answer to my question about the roles error.
Still, it would be nice to have more up-to-date instructions on how to
install PostgreSQL on OS X. Any pointers would be much appreciated!
TIA!
kj
On 4/15/07, Kynn Jones [EMAIL PROTECTED] wrote:
I'm trying to install PostgreSQL
Hi. I'm looking for Pg- and OSX-friendly software for generating schema
diagrams. It its most basic level, I'm looking for the graphics counterpart
of pg_dump -s, although it would be nice if the program could take as input
the name of a file containing an arbitrary schema definition (i.e. not
On 3/15/07, Stephen Frost [EMAIL PROTECTED] wrote:
* Kynn Jones ([EMAIL PROTECTED]) wrote:
One big question I have is, is this completely read-only?
Sorry, I should have made this clear: the access we had in mind is
strictly read-only, and only a subset of the tables at that.
kj
the service.
That said, for this experimental feature to work at all, it is necessary to
have a solid way to automate the granting of access to those servers that
request it and meet our conditions.
kj
On 3/15/07, Stephen Frost [EMAIL PROTECTED] wrote:
* Kynn Jones ([EMAIL PROTECTED]) wrote:
On 3/15
I need advice, and a lot of it, from those with more experience, since
I have practically none. Please, let me know your opinion on the
following.
We have an in-house Postgres database that we would like to make
publicly accessible via a password-less login (user: anonymous). (We
already have
I have a Perl script that runs every night and updates a local Pg
database, sitting on a Linux server. (I'll refer to this database as
mydb in the following.)
The update process takes about 1 hour, so the script first builds a
temporary database called mydb_tmp. Once mydb_tmp is built and
I keep bumping against this situation:I have a main database A, and I want to implement a database B, that is distinct from A, but subordinate to it, meaning that it refers to data in A, but not vice versa.
I don't simply want to add new tables to A to implement B, because this unnecessarily
Thank you all for cluing me in onpg_putline and pg_endcopy. Much cleaner than my kluge.
kj
I have a Perl script that is supposed to make a large number of inserts in a PostgreSQL database. Performing individual inserts with SQL's INSERT command is too slow, however, I can use a COPY ... from stdin approach that is fast enough. Basically, I fork a psql process (yes, I'm on unix)and have
kj314159265358979
I know that one can store multiple psql commands and SQL statements in
a separate script file, and then source the script file, e.g. with
the \i command.
My question is, can I define variables in such a script file? E.g. can
I do something like the following unix-shell-like
101 - 110 of 110 matches
Mail list logo