Here's an example using plperl and global variables. The variables are
local to a session so you don't have to worry about the counters
interfering. If you need two counters in a session, just execute
reset_counter().
CREATE OR REPLACE FUNCTION reset_counter() RETURNS INT AS $$
$_SHARED{counter}
On Fri, 2005-02-25 at 09:20 -0800, Si Chen wrote:
> Thanks!
>
> Is there any documentation on how to upgrade to 8.0?
>
> Is it possible to upgrade from 7.4 to 8.0 while keeping a production
> database running "in place"? Or should I install 8.0 in another
> directory/machine and then restore t
Jeff Davis wrote:
Here's an example using plperl and global variables. The variables are
local to a session so you don't have to worry about the counters
interfering. If you need two counters in a session, just execute
reset_counter().
CREATE OR REPLACE FUNCTION reset_counter() RETURNS INT AS $$
$_
On Fri, Feb 25, 2005 at 15:12:07 -0800,
Si Chen <[EMAIL PROTECTED]> wrote:
> Hello everyone. Thanks for the answers earlier about the new 8.0 version.
>
> We have a client who is thinking about putting postgresql 8.0 on Windows
> 2003 Server, but he is concerned because this is the first versi
>Hello everyone. Thanks for the answers earlier about the new
>8.0 version.
>
>We have a client who is thinking about putting postgresql 8.0
>on Windows
>2003 Server, but he is concerned because this is the first version to
>run natively on windows. Are there any issues with 8.0 on Windows?
On Fri, Feb 25, 2005 at 21:19:34 +0100,
Berényi Gábor <[EMAIL PROTECTED]> wrote:
>
> I have a dotgeek.org free account, but they are about to leave
> PostgreSQL for MySQL which is too bad. Can you suggest me a
> free/cheap PostgreSQL host where I can test an open-source program?
> No web host
I am allowing my users to delete data from certain tables. However, to
be able to do a rollback of user changes, I decided to create another
"backup" schema that most data tables will copy data to, upon delete.
So basically what I have is:
public schema, in which there are two tables, A and B.
ba
On Sat, Feb 26, 2005 at 01:27:55AM -0800, Jeff Davis wrote:
> On Fri, 2005-02-25 at 09:20 -0800, Si Chen wrote:
> > Thanks!
> >
> > Is there any documentation on how to upgrade to 8.0?
> >
> > Is it possible to upgrade from 7.4 to 8.0 while keeping a production
> > database running "in place"?
On Fri, 2005-02-25 at 17:12, Si Chen wrote:
> Hello everyone. Thanks for the answers earlier about the new 8.0 version.
>
> We have a client who is thinking about putting postgresql 8.0 on Windows
> 2003 Server, but he is concerned because this is the first version to
> run natively on windows.
Bruno Wolff III <[EMAIL PROTECTED]> writes:
> Si Chen <[EMAIL PROTECTED]> wrote:
>> Are there any issues with 8.0 on Windows?
> I think the windows problems have been pretty minimal. To get an idea
> of the scope, you might take a look at the 8.0.1 release notes.
The problems we've *fixed* have
Sorry, I should have said 'vacuum analyze verbose'...
On Sat, 2005-02-26 at 00:45 -0500, Greg Stark wrote:
> Mike Harding <[EMAIL PROTECTED]> writes:
>
> > The following was run -immediately- after a vacuum.
>
> You realize "vacuum" doesn't update the statistics, right?
> You have to do "analyz
"Rick Schumeyer" <[EMAIL PROTECTED]> writes:
> Would some combination of triggers work instead?
Nope, you can't put triggers on a view, sorry. In theory a BEFORE
INSERT trigger would be a workable alternative to an ON INSERT rule
for redirecting insertions. (I think we disallow it at the moment
The world rejoiced as [EMAIL PROTECTED] ("Jim C. Nasby") wrote:
> On Sat, Feb 26, 2005 at 01:27:55AM -0800, Jeff Davis wrote:
>> On Fri, 2005-02-25 at 09:20 -0800, Si Chen wrote:
>> > Thanks!
>> >
>> > Is there any documentation on how to upgrade to 8.0?
>> >
>> > Is it possible to upgrade from 7
[EMAIL PROTECTED] presumably uttered the following on 02/25/05 19:14:
Yes, thank you, I corrected my function from statement level to row level.
This did get rid of the error message. However, I still get no output from
an OLD variable that should contain data: see the test variable in the
simple
14 matches
Mail list logo
