On Thu, Mar 14, 2002 at 09:08:55AM +0500, Hannu Krosing wrote:
> AFAIK some SQL/C type precompilers and other frontend tools for other
> databases do generate stored procedures for PREPAREd CURSORs.
You mean ECPG should/could replace a PEPARE statement with a CREATE
FUNCTION and then the usage of
Is there an easy way to test the lock on a user level lock without actually
issuing the lock?
I would like to use them, but there is only a LockAcquire() and
LockRelease().. There is no LockTest()..
I guess I could do:
IF LockAcquire() == 0:
"locked" do whatever if it is locked...
ELSE:
Vince Vielhaber <[EMAIL PROTECTED]> writes:
> There are really no other decent CMSs available that support
> PostgreSQL.
bricolage.thepirtgroup.com/
Mike.
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgr
Yep
> -Original Message-
> From: Bruce Momjian [mailto:[EMAIL PROTECTED]]
> Sent: Friday, 15 March 2002 5:20 AM
> To: Christopher Kings-Lynne
> Cc: Hackers
> Subject: Re: [HACKERS] privileges regression problem on freebsd/alpha
>
>
>
> Christopher, is this problem fixed now?
>
> -
Kyle wrote:
> On the subject on client/server compression, does the server
> decompress toast data before sending it to the client? Is so, why
> (other than requiring modifications to the protocol)?
>
> On the flip side, does/could the client toast insert/update data
> before sending it to the s
On the subject on client/server compression, does the server
decompress toast data before sending it to the client? Is so, why
(other than requiring modifications to the protocol)?
On the flip side, does/could the client toast insert/update data
before sending it to the server?
-Kyle
-
> > This isn't an issue for a SELECT nextval() standing on
> > its own AFAIK the result will not be transmitted to the
> > client until after the commit happens. But it would be
> > an issue for a select executed inside a transaction
> > block (begin/commit).
>
> The behavior of SELECT nextval()
Larry Rosenman <[EMAIL PROTECTED]> writes:
> Hackers: Is there any reason to NOT make --enable-syslog the default
> any more?
> I.E. can we change the sense of it to be --disable-syslog and have
> USE_SYSLOG defined by default?
I thought we'd agreed to do that already; at least Peter had indica
Ben Grimm <[EMAIL PROTECTED]> writes:
> The behavior of SELECT nextval() should not be conditional on being in or
> out of a transaction block.
Nonsense. The behavior of INSERT or UPDATE is "conditional" in exactly
the same way: you should not rely on the reported result until it's
committed.
On 14 Mar 2002 21:17:05 +
"Oliver Elphick" <[EMAIL PROTECTED]> wrote:
> On Thu, 2002-03-14 at 20:13, Jie Liang wrote:
> > I did everything as you did, however, when start the postmaster,
> > I got following:
> > FATAL 1:'syslog' is not a valid option name.
>
> Then you haven't configured
I'm working on an update to contrib/dblink which would allow
INSERT/UPDATE/DELETE statements in addition to SELECT statements against
a remote database.
In the current version, only SELECT is possible because the SQL
statement passed to the function gets "DECLARE mycursor CURSOR FOR "
appende
On Thursday 14 March 2002 22:40, Bruce Momjian wrote:
> > > I guess some of these weren't introduces by you, but if someone is
> > > going to fix this, he might as well take care of these.
> >
> > Will submit another patch in the morning (it's late here).
>
> Ian, do you have another version of th
Neil Conway wrote:
> Hi all,
>
> I'm working on implementing unique hash indexes. I've got most of the
> code finished, but I'm stumped on how to implement the remainder. Since
> I'm still a newbie to the Postgres code, so any pointers or help would
> be much appreciated.
>
> I've been able to b
> > I guess some of these weren't introduces by you, but if someone is going
> > to fix this, he might as well take care of these.
>
> Will submit another patch in the morning (it's late here).
Ian, do you have another version of this patch ready?
--
Bruce Momjian| h
OK, I no one can seem to come up with an improved file format for
pg_hba.conf so I am going to continue in the direction outlined in this
email --- basically remove the auth_argument column and make it
'auth_type=auth_arg' and add a username column, plus add the ability for
the username and data
Christopher, is this problem fixed now?
---
Christopher Kings-Lynne wrote:
> Hi all,
>
> Just tested latest CVS on my freebsd/alpha. Only one test failed, and
> that's privileges related...
>
> *** ./expected/privileges.
On Thu, 2002-03-14 at 14:29, Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> >> This may be of value for users with low bandwidth connectivity to their
> >> servers or where bandwidth may already be at a premium.
>
> > But don't slow links do the compression themselves, like PPP ove
On Thu, 2002-03-14 at 14:14, Neil Conway wrote:
> On Thu, 2002-03-14 at 14:35, Bruce Momjian wrote:
> > Greg Copeland wrote:
> >
> > Checking application/pgp-signature: FAILURE
> > -- Start of PGP signed section.
> > > Well, it occurred to me that if a large result set were to be identified
> > >
On Thu, 2002-03-14 at 13:35, Bruce Momjian wrote:
> Greg Copeland wrote:
>
> Checking application/pgp-signature: FAILURE
> -- Start of PGP signed section.
> > Well, it occurred to me that if a large result set were to be identified
> > before transport between a client and server, a significant a
Bruce Momjian <[EMAIL PROTECTED]> writes:
>> This may be of value for users with low bandwidth connectivity to their
>> servers or where bandwidth may already be at a premium.
> But don't slow links do the compression themselves, like PPP over a
> modem?
Even if the link doesn't compress, shovin
You can get some tremendous gains by compressing HTTP sessions - mod_gzip
for Apache does this very well.
I believe SlashDot saves in the order of 30% of their bandwidth by using
compression, as do sites like http://www.whitepages.com.au/ and
http://www.yellowpages.com.au/
The mod_gzip trick is
On Thu, 2002-03-14 at 14:35, Bruce Momjian wrote:
> Greg Copeland wrote:
>
> Checking application/pgp-signature: FAILURE
> -- Start of PGP signed section.
> > Well, it occurred to me that if a large result set were to be identified
> > before transport between a client and server, a significant a
Bruce Momjian wrote:
>
> Greg Copeland wrote:
>
> Checking application/pgp-signature: FAILURE
> -- Start of PGP signed section.
> > Well, it occurred to me that if a large result set were to be identified
> > before transport between a client and server, a significant amount of
> > bandwidth m
Bruce Momjian wrote:
>
> Greg Copeland wrote:
> > Well, it occurred to me that if a large result set were to be identified
> > before transport between a client and server, a significant amount of
> > bandwidth may be saved by using a moderate level of compression.
> > Especially with something li
"Dave Cramer" <[EMAIL PROTECTED]> writes:
> I noticed a message asking if this scenario was consistent with the
> other reports, and yes it is. We have seen this occuring on our system
> with versions as old as 7.0.
Given that these are WAL bugs, they could not predate 7.1.
Greg Copeland wrote:
Checking application/pgp-signature: FAILURE
-- Start of PGP signed section.
> Well, it occurred to me that if a large result set were to be identified
> before transport between a client and server, a significant amount of
> bandwidth may be saved by using a moderate level of
Well, it occurred to me that if a large result set were to be identified
before transport between a client and server, a significant amount of
bandwidth may be saved by using a moderate level of compression.
Especially with something like result sets, which I tend to believe may
lend it self well
Greg Copeland wrote:
> Just curious, and honestly I haven't looked, but is there any form of
> compression between clients and servers? Has this been looked at?
This issues has never come up before. It is sort of like compressing an
FTP session. No one really does that. Is there value in tryi
On Thu, 14 Mar 2002, Tom Lane wrote:
> Vince Vielhaber <[EMAIL PROTECTED]> writes:
> >> What's your definition of "other dbs"? The above statement is quite
> >> clearly in violation of the SQL92 and SQL99 specifications:
>
> > And nowhere does it say that cannot be qualified with
> > the table
I noticed a message asking if this scenario was consistent with the
other reports, and yes it is. We have seen this occuring on our system
with versions as old as 7.0.
Glad to see someone has finally nailed this one.
Dave
---(end of broadcast)---
Vince Vielhaber <[EMAIL PROTECTED]> writes:
>> What's your definition of "other dbs"? The above statement is quite
>> clearly in violation of the SQL92 and SQL99 specifications:
> And nowhere does it say that cannot be qualified with
> the table name in front of it.
Au contraire, that is EXACT
Turbo Fredriksson wrote:
>>"Oliver" == Oliver Elphick <[EMAIL PROTECTED]> writes:
>>
>
> Oliver> On Thu, 2002-03-14 at 13:00, Turbo Fredriksson wrote:
> >> With '\d table' I get the columns, types and modifiers. Also
> >> the Primary key, Indexes etc are shown.
> >>
>
"Tom Pfau" <[EMAIL PROTECTED]> writes:
> I'm concerned that the discussion here has been of the opinion that
> since no records were written to the database using the value retrieved
> from the sequence that no damage has been done.
Um, you certainly didn't hear me saying that ;-)
There are two
On Thu, 14 Mar 2002, Stephan Szabo wrote:
>
> ::= !! See the Syntax Rules
>
> ::=
>
> |
> identifier start is a simple latin letter, a letter in the character
> repertoire that's in use, a syllable in the repertoire or an ideograph in
> the repe
On Thu, 14 Mar 2002, Vince Vielhaber wrote:
> On Thu, 14 Mar 2002, Rod Taylor wrote:
>
> > As snipped from:
> > http://archives.postgresql.org/pgsql-bugs/2000-10/msg00030.php (All
> > my stuff is in paper form)
> > What's your definition of "other dbs"? The above statement is quite
> > clearl
On Thu, 14 Mar 2002, Jean-Paul ARGUDO wrote:
> This daemon wakes up every 5 seconds. It scans (SELECT...) for new
> insert in a table (lika trigger). When new tuples are found, it
> launches the work. The work consist in computing total sales of a big
> store...
You might find it worthwhile to i
"Jose Javier Gutierrez" <[EMAIL PROTECTED]> writes:
> com.kristinaIbs.persistence.ExceptionPersistence: ManagerPersistencePool
> (getConnection).Connection refused. Check that the hostname and port is
> correct, and that the postmaster is running with the -i flag, which enables
> TCP/IP networkin
"Seung Hyun Jeong" <[EMAIL PROTECTED]> writes:
> I am experimenting on performance evaluation for some queries based on
> PostgreSQL.
> To give fair conditions to each queries, I try to clear buffer of PostgreSQL
> before running each queries.
> I think the following function in .../backend/stora
Quoting Oliver Elphick <[EMAIL PROTECTED]>:
> On Thu, 2002-03-14 at 13:28, Turbo Fredriksson wrote:
> > Oliver> Just do \d again on the key index name:
> >
> > Oliver> bray=# \d org_contact
> > Oliver> bray=# \d org_contact_pkey
> >
> > Cool. Works fine in 7.2, but not 7.1.3 (which
On Thu, 14 Mar 2002, Rod Taylor wrote:
> Out of curiosity, does SyBase allow you to qualify it with
> schema.table.column?
Just tried it... Yes.
Vince.
--
==
Vince Vielhaber -- KA8CSHemail: [EMAIL PROTECTED]http:/
Out of curiosity, does SyBase allow you to qualify it with
schema.table.column?
--
Rod Taylor
This message represents the official view of the voices in my head
- Original Message -
From: "Vince Vielhaber" <[EMAIL PROTECTED]>
To: "Rod Taylor" <[EMAIL PROTECTED]>
Cc: "Peter Eisentraut" <[
Just curious, and honestly I haven't looked, but is there any form of
compression between clients and servers? Has this been looked at?
Greg
signature.asc
Description: This is a digitally signed message part
On Thu, 14 Mar 2002, Rod Taylor wrote:
> As snipped from:
> http://archives.postgresql.org/pgsql-bugs/2000-10/msg00030.php (All
> my stuff is in paper form)
> What's your definition of "other dbs"? The above statement is quite
> clearly in violation of the SQL92 and SQL99 specifications:
And
As snipped from:
http://archives.postgresql.org/pgsql-bugs/2000-10/msg00030.php (All
my stuff is in paper form)
What's your definition of "other dbs"? The above statement is quite
clearly in violation of the SQL92 and SQL99 specifications:
::=
INSERT INTO
On Thu, 14 Mar 2002, Rod Taylor wrote:
> Why not send in your changes to PostNuke along with the appropriate
> section from the SQL specs?
>
> Surely they'll apply a reasoned patch which improves conformance to
> the SQL standard and doesn't break anything in the process. I'd
> suspect both SyBa
> Cool. Works fine in 7.2, but not 7.1.3 (which we're running on our
> production systems)...
> Any idea how to do this on 7.1.3?
contact=# \d t_operation
Table "t_operation"
Attribute | Type | Modifier
Why not send in your changes to PostNuke along with the appropriate
section from the SQL specs?
Surely they'll apply a reasoned patch which improves conformance to
the SQL standard and doesn't break anything in the process. I'd
suspect both SyBase, and MySQL can also take insert into foo (a) as
Hi friends,
I have problems with postgres.jar and tomcat. I have de follow exception :
- Excepcion de persistencia:
com.kristinaIbs.persistence.ExceptionPersistence: ManagerPersistencePool
(getConnection).Connection refused. Check that the hostname and port is
correct, and that the postma
On Wed, 2002-03-13 at 21:18, Jean-Paul ARGUDO wrote:
> Hi all,
>
>
> Here are the results of our survey on a migration from Oracle 8.0 / W$
> NT4 SP5 to PostgreSQL 7.2 / Red Hat 7.2.
>
> You'll probably remember of a thread I initiated in this list a couple
> of weeks ago, this is the same surv
On Thu, 2002-03-14 at 02:30, Zeugswetter Andreas SB SD wrote:
>
> > So this finaly makes the batch work taking 300% the time Oracle needs.
> > We clearly see our ECPG programs waits for PostgreSQL in the functions
> > were CURSORs are opened. Then, we know the problem is not in ECPG but in
> > PG
On Thu, 2002-03-14 at 11:20, Jean-Paul ARGUDO wrote:
> > > Unless you need to run concurrent vacuums,
>
> Forgot to say too that de x3 ratio is based only on batch mode. Daemon
> mode is as faster as Oracle (wow!).
>
> Forgot to say too that in batch mode we launch concurrent vacuum analyze
> on
On Wed, 13 Mar 2002, Bruce Momjian wrote:
> You bet, but it would be done in the backend, not in jdbc. Is that OK?
Theoretically this is okay. I am more comfortable in Java than in C and I
hadn't looked at the backend code at all, but I'll take a peek and see if
it looks like something I'd feel
On Wed, 13 Mar 2002, Peter Eisentraut wrote:
> Vince Vielhaber writes:
>
> > For example:
> >
> > insert into foo(foo.a) values(1);
> >
> > fails because the table name is used. Update statements also include the
> > table name. Both fail. Does anyone know of a workaround?
>
> Completely loudl
> "Oliver" == Oliver Elphick <[EMAIL PROTECTED]> writes:
Oliver> On Thu, 2002-03-14 at 13:00, Turbo Fredriksson wrote:
>> With '\d table' I get the columns, types and modifiers. Also
>> the Primary key, Indexes etc are shown.
>>
>> But if I want to know WHAT the primary k
On Thu, 2002-03-14 at 13:00, Turbo Fredriksson wrote:
> With '\d table' I get the columns, types and modifiers. Also
> the Primary key, Indexes etc are shown.
>
> But if I want to know WHAT the primary key 'is pointing to',
> how would I do that (ie, what is the primary key)?
Just do \d again on
Welcome to the pgsql-hackers mailing list!
Your password at PostgreSQL User Support Lists is
tsXRQ6
To leave this mailing list, send the following command in the body
of a message to [EMAIL PROTECTED]:
approve tsXRQ6 unsubscribe pgsql-hackers archive@jab.org
This command will work even if your
56 matches
Mail list logo
