Added to TODO:
* Have pg_dump -C dump database location and encoding
information
Jim Buttafuoco writes:
will do.
While you're at it, at least the encoding parameter should be saved as
well. Take a peek at what pg_dumpall saves.
Jim Buttafuoco writes:
On Thu, 11 Oct 2001, Balaji Venkatesan wrote:
Now i need to install DBD For PGSQL .Is
this the driver i have to work on for pgsql ?.
Or do I have any other option to connect to pgsql
from perl . Indeed i've found out an other way
to use Pg driver
Balaji Venkatesan [EMAIL PROTECTED] writes:
I have installed latest DBI from www.cpan.org
Now i need to install DBD For PGSQL .Is
this the driver i have to work on for pgsql ?.
If you want to use DBI then you should get the DBD::Pg driver from
CPAN. (Yes, it is on
Tom,
Thanks for the prompt reply. Following is the postgresql log output:
DEBUG: ProcessQuery
DEBUG: CommitTransactionCommand
DEBUG: StartTransactionCommand
DEBUG: query: SELECT Oid FROM pg_index i WHERE i.indisprimary AND
i.indrelid = '3527162388'::oid
DEBUG: ProcessQuery
DEBUG:
steve [EMAIL PROTECTED] writes:
DEBUG: query: SELECT c.relname FROM pg_index i LEFT OUTER JOIN pg_class c
ON c.oid = i.indexrelid WHERE i.indrelid = 3527162388AND i.indisprimary
ERROR: dtoi4: integer out of range
The 3527162388AND is exactly as shown in the log, with no space between the
i've had similar problems before. Looks like some thing is in a transaction,
blocked on something else. Then vacuum comes in, locks half the tables, and
then gets stuck on a table that the transaction has modified. Now most of
your other transactions will block forever. Then the connection limit
Michael Meskes [EMAIL PROTECTED] writes:
A customer's machine hangs from time to time. All we could find so far is
that postgres seems to be in state idle in transaction:
You evidently have some client applications holding open transactions
that have locks on some tables. That's not a
Bruce Momjian wrote:
$newSerialID = nextval('person_id_seq');
INSERT INTO person (id, name) VALUES ($newSerialID, 'Blaise Pascal');
Is this correct Perl? I don't see a nextval() function in Perl. Can
you call SQL server-side functions natively from Perl?
Ofcourse not.
Bruce Momjian writes:
Our FAQ, item 4.16.2 has:
$newSerialID = nextval('person_id_seq');
INSERT INTO person (id, name) VALUES ($newSerialID, 'Blaise Pascal');
Is this correct Perl?
No. I always thought it was pseudo code. I think it's fine.
--
Peter Eisentraut [EMAIL
When adding an index to a (quite large, ~2 million rows) table
PostgreSQL continues to do sequential lookups until VACUUM ANALYZE is
run. Naturally performance is poor.
The CREATE INDEX statement takes considerable time.
Seen with 7.1.3 on Intel Linux (RedHat 7.0 7.1 and Solaris 2.6.
In the
I found a non-existent option -list described in the doc of
libpgtcl's pg_result procedure. Shall we remove it from the docs?
Yes, removed. Thanks.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 853-3000
+ If your life is a
A customer's machine hangs from time to time. All we could find so far is
that postgres seems to be in state idle in transaction:
postgres 19317 0.0 0.3 8168 392 ?SOct05 0:00
/usr/lib/postgresql/bin/postmaster -D /var/lib/postgres/data
postgres 19983 0.0 0.8 8932 1020 ?
Bruce Momjian [EMAIL PROTECTED] writes:
OK, that makes sense. My only question is how many platforms _don't_
have syslog. If it is only NT and QNX, I think we can live with using
it by default if it exists.
There seems to be a certain amount of confusion here. The proposal at
hand
Patch applied. Thanks Tatsuo and Tom.
Tatsuo Ishii [EMAIL PROTECTED] writes:
As you can see, psql reconnect as any user if the password is same as
foo. Of course this is due to the careless password setting, but I
think it's better to prompt ANY TIME the user tries to switch to
Tatsuo,
Did you ever commit this new function? I just tried a 'select
pg_client_encoding()' and it told me that there was no such function.
This was on sources that I pulled and built two days ago.
I was planning on changing the JDBC code to use this function instead of
Bruce Momjian [EMAIL PROTECTED] writes:
Would someone give me a status on this?
I don't think we need any code changes. If we decide to deprecate -o
(or anything else), it's just a documentation change. So we can argue
about it during beta ...
If we notify of the impending deprecation now,
Can I ask about the status of this?
Hi all,
while working on a new project involving PostgreSQL and making some
tests, I have come up with the following output from psql :
lang | length | length | text| text
--+++---+---
isl | 7 |
Tatsuo Ishii [EMAIL PROTECTED] writes:
This is really annoying since:
o these code fragments actually controls the optimization efforts for
subqueries and views, not related to GEQO at all. So using GEQO
parameters for this kind of purpose seems abuse for me.
But GEQO_RELS is
Reinoud van Leeuwen [EMAIL PROTECTED] writes:
I have a table that contains almost 8 milion rows. The primary key is a
sequence, so the index should have a good distribution. Why does the
optimizer refuse to use the index for getting the maximum value?
The optimizer has no idea that
Can I get a status on this?
On Sun, 23 Sep 2001, Tom Lane wrote:
Note: I'm not convinced that relfilenode and pg_class.oid are each
used in exactly the right spots. Once we have cases where they can
differ, we may well find some bugs to flush out. But that needs to
happen anyway,
Bruce Momjian [EMAIL PROTECTED] writes:
Can I get a status on this?
It's not gonna happen for 7.2, I think ...
regards, tom lane
---(end of broadcast)---
TIP 6: Have you searched our list archives?
Bruce Momjian [EMAIL PROTECTED] writes:
Would someone give me a status on this?
I don't think we need any code changes. If we decide to deprecate -o
(or anything else), it's just a documentation change. So we can argue
about it during beta ...
If we notify of the impending
Bruce Momjian [EMAIL PROTECTED] writes:
I don't think we can remove -o behavior during beta because it will
affect people using -S in startup scripts.
That was *not* the proposal under discussion. The proposal was to
warn people in the 7.2 documentation that we plan to remove -o in 7.3.
Would someone give me a status on this?
---
Hi all,
There seem to be a few namespace conflicts for the options of postgres
and postmaster. The one's I could identify from the man pages are :
-i -N -o -p -S -s
Plus or minus?
Is there a standard for this? We are printing date/time using Posix
conventions, which are opposite from the SQL conventions for setting
time zone (which we don't yet support, since it is fundamentally useless
;) I apparently implemented one, and you expect the other.
peter=#
Just updated...
peter=# SELECT EXTRACT(DOW FROM TIMESTAMP '2001-02-16 20:38:40');
ERROR: Timestamp with time zone units 'dow' not recognized
This is documented to work.
Ah, I broke this with some recent additions to implement more ISO
conventions (I changed the behavior of the date/time
26 matches
Mail list logo
