Tom Lane writes:
Not exactly. It is possible to use PGHOST but you also can add the hostname
to the dbname.
Have you tried it lately? I suspect that you are depending on code that
is not in libpq's current sources anymore. I fully agree with Peter E's
reasons for removing it, too. We
Thanks, Tom, and also to Alex Pilosov for his answer.
I was extrapolating from the plpgsql docs, which I probably didn't
understand correctly.
Programming By Example (which is what we non-programmers are obliged to do)
doesn't work so well when the docs are somewhat sparse.
Are there any plans to
I think that under 7.1, pg_log is not so critical anymore, but I'm not
sure. Vadim, any comment?
Still critical till we implement UNDO and true changes rollback on
transaction abort.
Vadim
Peter Eisentraut [EMAIL PROTECTED] writes:
Have you tried it lately? I suspect that you are depending on code that
is not in libpq's current sources anymore. I fully agree with Peter E's
reasons for removing it, too. We do not need to overload the definition
of libpq's dbname parameter.
On 5 Jan 01, at 14:37, Scott Teglasi wrote:
When I add a record, I fill in the relevant fields, but when I
proceed
to the next row, the row I just added shows "#Deleted" in all of
the
columns. It continues to do this as I add records. When I close
the
table, then reopen it, my data is
I cannot seem to insert hex values into an int column.
I must be doing something really stupid wrong, but I
can't see it.
insert into mytable (intcolumn) values (0xaabbcc);
parser error at "xaabbcc"
insert into mytable (intcolumn) values ('0xaabbcc');
pg_atoi...can't part
Adam Haberlach [EMAIL PROTECTED] writes:
Is there any simple way for me to get a list of all large objects
in a database, so I can see if there are actually rows referring to them
and delete the ones that were not unlinked earlier?
Look at the vacuum_lo contrib module.
BTW, I believe
after i ran vacuum analyze, i see that all my database directories with
respect to their database names have changed to all numbers:
# ls -l /var/pgsql/data
total 17
-rw--- 1 pgsql wheel 4 Dec 30 15:45 PG_VERSION
drwx-- 6 pgsql wheel 512 Jan 8 05:28 base
drwx-- 2 pgsql
Dangling large objects? I thought this was a family list. :-)
-- Brett
PS. Sorry, couldn't resist...
http://www.chapelperilous.net/~bmccoy/
---
Unnamed Law:
If it happens, it
mnogosearch only does inserts into the database, it doesn't check for a
previous occurance of the record first, so you are getting what is
expected ...
I think they work under teh guise that better return an error then do two
queries ...
On Mon, 8 Jan 2001, Thomas T. Thai wrote:
i'm starting
Thomas T. Thai writes:
after i ran vacuum analyze, i see that all my database directories with
respect to their database names have changed to all numbers:
is this normal?
Yes, and it surely was like that before the vacuum analyze as well. This
is new with 7.1.
--
Peter Eisentraut
how does one change the time intervals between 'checkpoints'?
What is there for a user or admin or programmer to know about the new WAL
stuff? What all does it do? Does it allow for an audit file to be created,
which can be used to playback and/or rewind the transactions on the database
by user/admin commands? How do checkpoints limit or affect how
Quick question: Is there a way to find out how many rows an UPDATE
affected in pl/pgsql?
Thanks
Hi all,
As I not familiar with the linux newsgroups and mailing lists, can
anyone give me some
guidance as to where I should post details of a java development job?
It's a Java GUI application which interfaces to a PostgreSQL database
backend
through JDBC.
Regards and best wishes,
Justin
I looked through all the docs, and I couldn't find a function which
would simply DES encrypt a string. Is DES not implemented in
Postgres? Or am I just not finding the function?
Thanks
Lee Joramo [EMAIL PROTECTED] writes:
[PostgreSQL 6.5.2 on powerpc-unknown-linux-gnu, compiled by gcc 2.95.2]
Hm. Did you compile at -O0? Pre-7.1 PG is known to have a lot of
problems on PPC if compiled with any optimization at all.
The 'classifieds.dat' consists of about 2200 lines. I have
In this case the planner is doing *exactly* the right thing; it is
smarter than you are. If you want to prove it, force the planner to
use an indexscan by doing SET ENABLE_SEQSCAN TO OFF. Then time the
query, and compare the runtime against the seqscan version.
The bottom line here is
"Robert B. Easter" [EMAIL PROTECTED] writes:
What is there for a user or admin or programmer to know about the new WAL
stuff?
Vadim is the man who ought to answer this (and he's on the hook to write
a lot of documentation before 7.1 ships ;-)). But my understanding is
that as of 7.1, WAL
19 matches
Mail list logo
