.
The 1st one temporarily changes CurrentResourceOwner to
CurTransactionResourceOwner during catalog cache handling.
The 2nd one allocates a new resource owner for held portals.
Both fix the crash in my test case.
regards,
Hiroshi Inoue
diff --git a/src/backend/access/common/printtup.c b/src
Bruce Momjian wrote:
Hiroshi Inoue wrote:
Bruce Momjian wrote:
Where are we on this issue?
Oops I forgot it completely.
I have a little improved version and would post it tonight.
Ah, very good. Thanks.
Attached is an improved version.
regards,
Hiroshi Inoue
? formatting.patch
Bruce Momjian wrote:
Where are we on this issue?
Oops I forgot it completely.
I have a little improved version and would post it tonight.
regards,
Hiroshi Inoue
---
Hiroshi Inoue wrote:
Tom Lane wrote:
Alvaro
examine localeconv()
output.
Attached is a patch to the current CVS.
It uses a similar way like LC_TIME stuff does.
regards,
Hiroshi Inoue
Index: pg_locale.c
===
RCS file: /projects/cvsroot/pgsql/src/backend/utils/adt/pg_locale.c,v
of FE/BE procotol?
regards,
Hiroshi Inoue
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
in Initialize
ClientEncoding() and unbind the codeset if necessary
in SetDatabaseEncoding().
Comments?
regards,
Hiroshi Inoue
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Tom Lane wrote:
Hiroshi Inoue in...@tpf.co.jp writes:
I'm thinking of the following steps in the backend code.
1.Set LC_MESSAGES to C until the client_encoding is
determined.
2.When a client_encoding is specifed in the startup
message, bind the corrsponding codeset to the
textdomain
references the client_encoding included in
the startup message.
regards,
Hiroshi Inoue
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Tom Lane wrote:
Peter Eisentraut pete...@gmx.net writes:
Bruce Momjian wrote:
Can someone comment on this?
Looks like a horrible hack to me. Recoding stuff to the client encoding
in the server outside the existing recoding mechanism looks pretty evil
to me. Plus, it does not address
driver can get
properly localized password error messages.
regards,
Hiroshi Inoue
Index: postmaster/postmaster.c
===
RCS file: /projects/cvsroot/pgsql/src/backend/postmaster/postmaster.c,v
retrieving revision 1.570
diff -c -c -r1.570
implementation. Because we have the separate LIMIT and OFFSET we can
fix it while giving people a solution that will work for all versions.
If we don't fix it, all MySQL queries that are ported will be broken.
But it seems absurd to trouble existent PG users instead.
regrads,
Hiroshi Inoue
Tom Lane wrote:
Hiroshi Inoue [EMAIL PROTECTED] writes:
One backend would be blocked by another one because reindex_relation
calls reindex_index and reindex_index grabs an ExclusiveLock on the
relation.
Am I missing anything ?
It'd be okay if you *held* the lock throughout. Grabbing
Tom Lane wrote:
Hiroshi Inoue [EMAIL PROTECTED] writes:
Where do I release the lock ?
I'd say you shouldn't release it at all.
As far as I see I'm not releasing it.
regards,
Hiroshi Inoue
---(end of broadcast)---
TIP 4: Don't 'kill -9
Tom Lane wrote:
Hiroshi Inoue [EMAIL PROTECTED] writes:
I'd say you shouldn't release it at all.
As far as I see I'm not releasing it.
Oh, I hadn't looked closely at reindex_index. Hmm... okay, you are
holding the lock acquired there.
Yes reindex_index is guarding itself
like REINDEX only grabs AccessShareLock on the target
relation, which seems very wrong.
Sorry I couldn't find where AccessShareLock is grabbed now.
AccessExclusiveLock is acquired in reindex_index but do you
mean it's too late ?
regards,
Hiroshi Inoue
---(end
-3] "phon"
SWORD
-3 DIAG [IM001] [Microsoft][ODBC
Driver Manager] Driver does not support this function (0)
Hmm SQLTablePrivleges() isn't implemented
yet.
It seems at least one of the
cause.
I'm not sure if I could implement it at
once.
Are you in a hurry ?
don't, I tried to insert the same record on PSQL and I get an error, could
it be the ODBC driver?
Please help me, if you know...
Try the latest ODBC driver at http://www.greatbridge.org/project/pgadmin/.
It includes an change about error reporting.
regards,
Hiroshi Inoue
(and without -S) and see what gets logged in its stderr output.
BTW what version of psqlodbc driver are you using ?
regards,
Hiroshi Inoue
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
commit it
in a few days.
Regards,
Hiroshi Inoue
analyze;
NOTICE: Index idx_domain_name: NUMBER OF INDEX' TUPLES (305) IS NOT THE
SAME AS HEAP' (311).
Recreate the index.
VACUUM
This is a known bug.
Probably there's a long transaction somewhere.
It is fixed in 7.1.
Regards,
Hiroshi Inoue
ved in 7.1 though I'm not sure.
Regards.
Hiroshi Inoue
as follows.
1. Stop the postmaster running.
pg_ctl -w stop
2. Invoke a standalone postgres.
postgres -P -O your_database_name
3. recreate the indexes using REINDEX command.
reindex table pg_attribute force;
4. press cntrl-D to exit the program.
5. restart postmaster.
Regards.
Hiroshi
CTID
update myTable set ..=.. where CTID=..;
Note that CTIDs aren't of int type.
Regards.
Hiroshi Inoue
backends insert values
(500, 2) at the same time.
Regards.
Hiroshi Inoue
ion levels.
INSENSITIVE cursors aren't implemented yet. Cursors aren't INSENSITIVE
because they would see the changes made by the backend itself. It's also
regardless of transaction isolation levels.
Regards.
Hiroshi Inoue
is an example which doesn't release the reference count.
Neither CommitTransaction() nor AbortTransaction() is called after '\q'
begin;
declare myc cursor for select * from ..;
fetch in myc;
\q
Regards.
Hiroshi Inoue
[EMAIL PROTECTED]
and number)
cmax
ctid may be what you're looking for, but I don't understand very well how
these are used. Maybe someone else can say or you can experiment...
AFAIK,there's no pseudo-column like Oracle's rownum which is
dynamically allocated at execution time.
Regards.
Hiroshi In
about starting new transaction automatically after committing
"create user ..." at backend side if "create user" is the first command
of the transaction ?
Regards.
Hiroshi Inoue
[EMAIL PROTECTED]
lmost same as pg_upgrade.
However you should probably copy pg_log and pg_variable to
$PGDATA as pg_upgrade does.
In addtion if postmaster is running,you should shutdown before
processing 2).
Regards.
Hiroshi Inoue
[EMAIL PROTECTED]
3) Try to access the tables from there
-Original Message-
From: Peter Eisentraut [mailto:[EMAIL PROTECTED]]
Sent: Thursday, April 27, 2000 4:46 PM
To: Hiroshi Inoue
On Thu, 27 Apr 2000, Hiroshi Inoue wrote:
PostgreSQL's SERIALIZABLE isolation level would allow both inserts.
READ COMMITED isolation level wouldn't
30 matches
Mail list logo
