On Thu, Mar 25, 2004 at 08:24:59PM -0800, Sean Chittenden wrote:
You can't think that allowing the same name to appear
globally and locally is a good idea.
Actually, I do think it is a good idea.
If I say GRANT TO foo, who am
I granting privileges to?
SET username_precedence TO
Sean Chittenden [EMAIL PROTECTED] writes:
You can't think that allowing the same name to appear
globally and locally is a good idea.
Actually, I do think it is a good idea.
If I say GRANT TO foo, who am
I granting privileges to?
SET username_precedence TO LOCAL,GLOBAL; -- I like GLOBAL
Heikki Linnakangas wrote:
I haven't seen your patch yet, but the proposal looks good to me.
On Tue, 23 Mar 2004, Alvaro Herrera wrote:
Let the currently unused fourth state in pg_clog indicate a
committed subtransaction. In pg_clog there are two bits per
transaction,
Hi everyone:
I am using Postgresql 7.3.4 and found a problem
inserting "Timestamp" objects throughJDBC Prepared Statements when the time
zone is set to Canada/Newfoundland (3 hours and30 minutes from MGT). I am
trying to insert "new Timestamp(0L)" into one of the fields.The database
Hello,
Both phpPgAdmin (me) and the pgAdmin team have added or have thought
about adding some 'schema analysis' features to our products. If
pg_advisor is available, I certainly won't bother and I will just
recommend to people that they install it.
Ok.
A more precise question is: on the
After a long battle with technology, [EMAIL PROTECTED] (Marc G. Fournier), an
earthling, wrote:
On Tue, 23 Mar 2004, Sailesh Krishnamurthy wrote:
Which brings me to another question .. has anybody considered using
subversion instead of CVS ?
Why? not that I'm for a chance from something
a wrote:
Hi,
Is it have any tools or control let delphi can direct connet to postgresql
not only use odbc?
Thank!!
Gary
take a look at
www.zeoslib.net
www.microolap.com/dac/postgresdac.htm
dbexpress :
www.vitavoom.com
Daniel
---(end of
I'm currently working on a student research project that is supervised by a
professor from my university. This project duration is 2 semesters. The
topic is to implement the two missing SQL3 standard triggers functionalities
in Postgresql, ¡®triggers on columns¡¯ and ¡®referencing old or new
Maybe I missed something, but it seemed to me that strings are appended
on to the other, and there is no way back.
But the string list is not constructed until the error actually occurs.
You don't need a pop at that point --- the call stack is what it is.
I think you are imagining that
You can't think that allowing the same name to appear
globally and locally is a good idea.
Actually, I do think it is a good idea.
If I say GRANT TO foo, who am
I granting privileges to?
SET username_precedence TO LOCAL,GLOBAL; -- I like GLOBAL more than
CLUSTER
GRANT TO foo;
SET
Richard Huxton [EMAIL PROTECTED] writes:
Maybe it's me being slow, but are we not being over-complicated here? What's
wrong with saying database D1 looks up users in local table, D2 in the
global table. If you are connected to D1, then no-one can see the global
userlist.
Hmm. That would
On Friday 26 March 2004 15:09, Tom Lane wrote:
Sean Chittenden [EMAIL PROTECTED] writes:
Agreed, but if a cluster is using LOCAL USERs, I doubt highly that
CLUSTER/GLOBAL users would be in use much beyond super users. -sc
Exactly my point. I think that it might be possible for a
Sean Chittenden [EMAIL PROTECTED] writes:
Another solution would be to have CREATE USER done by a local admin
create users in the form of '[EMAIL PROTECTED]'. This prevents
duplicate usernames and allows us to use the current hack of local
database users.
Yeah, I think it would be
I have some results from DBT-2 testing PostgreSQL with difference block
sizes against different lvm stripe widths on Linux. I've found that
iostat appears to report more erratic numbers as the block size of the
database increases but I'm not able to see any reason for it.
I have pg_xlog on a
Richard Huxton [EMAIL PROTECTED] writes:
Maybe it's me being slow, but are we not being over-complicated here?
What's
wrong with saying database D1 looks up users in local table, D2 in the
global table. If you are connected to D1, then no-one can see the
global
userlist.
Hmm. That would
I've just found out the hard way that Postgres doesn't even build on
recent gcc releases for 64-bit HPPA. The reason is that the compiler
now notices and complains about alignment errors that will lead to
core dump at runtime, and GIST has got some. The particular code that
fails to compile is
On Fri, 19 Mar 2004, Denis Khabas wrote:
Hi everyone:
I am using Postgresql 7.3.4 and found a problem inserting Timestamp
objects through JDBC Prepared Statements when the time zone is set to
Canada/Newfoundland (3 hours and 30 minutes from MGT). I am trying to
insert new Timestamp(0L)
We have a customer who reports a weird problem.
Too often the App. Server fails to connect to the database.
Sometimes the scheduled vacuum fails as well.
The error message is always the same:
FATAL: The database system is shutting down
But from what I see no one is trying to shut down the
Denis,
This is more appropriate for the jdbc mail list.
--Barry
Denis Khabas wrote:
Hi everyone:
I am using Postgresql 7.3.4 and found a problem inserting Timestamp objects through
JDBC Prepared Statements when the time zone is set to Canada/Newfoundland (3 hours and
30 minutes from MGT). I
Michael Brusser [EMAIL PROTECTED] writes:
The error message is always the same:
FATAL: The database system is shutting down
But from what I see no one is trying to shut down the database at this time.
*Something* has sent the postmaster a shutdown signal --- either
SIGINT or SIGTERM. Look
Hey,
We have many machines that run Solaris. I know that there are patches
out there for some of the bugs in 7.4.2 for Solaris but I was wondering
what the timeline for an official 7.4.3 was?
Sincerely,
Joshua D. Drake
--
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Joshua D. Drake [EMAIL PROTECTED] writes:
We have many machines that run Solaris. I know that there are patches
out there for some of the bugs in 7.4.2 for Solaris but I was wondering
what the timeline for an official 7.4.3 was?
Don't hold your breath ... 7.4.2 was only a couple weeks ago, and
Another solution would be to have CREATE USER done by a local admin
create users in the form of '[EMAIL PROTECTED]'. This prevents
duplicate usernames and allows us to use the current hack of local
database users.
Yeah, I think it would be reasonable to leave that facility as-is and
invent a
On 26 Mar, Bruce Momjian wrote:
[EMAIL PROTECTED] wrote:
On 26 Mar, Manfred Spraul wrote:
[EMAIL PROTECTED] wrote:
Compare file sync methods with one 8k write:
(o_dsync unavailable)
open o_sync, write 6.270724
write, fdatasync13.275225
[EMAIL PROTECTED] wrote:
On 26 Mar, Manfred Spraul wrote:
[EMAIL PROTECTED] wrote:
Compare file sync methods with one 8k write:
(o_dsync unavailable)
open o_sync, write 6.270724
write, fdatasync13.275225
write, fsync, 13.359847
On 26 Mar, Manfred Spraul wrote:
[EMAIL PROTECTED] wrote:
Compare file sync methods with one 8k write:
(o_dsync unavailable)
open o_sync, write 6.270724
write, fdatasync13.275225
write, fsync, 13.359847
Odd. Which filesystem, which
On Fri, Mar 26, 2004 at 07:25:53AM +0100, Manfred Spraul wrote:
Compare file sync methods with one 8k write:
(o_dsync unavailable)
open o_sync, write 6.270724
write, fdatasync13.275225
write, fsync, 13.359847
Odd. Which filesystem,
27 matches
Mail list logo
