Thread: PgManage update
Hello, Currently we have the following working: Multiple server connection: 100% SSL Connectivity for secure management: 100% Over the Wire backup: 100% Over the Wire restore: 100% User management: 100% Group Management: 100% Query exectution: 50% Database management: 75% Table Management: 75% Platforms: Linux x86: 100% Win 32: 100% Solaris: 75% Sincerely, Joshua Drake P.S. There are new screenshots at: http://www.commandprompt.com/entry.lxp?lxpe=126 -- -- by way of pgsql-general@commandprompt.com http://www.postgresql.info/ http://www.commandprompt.com/
Is this open-source software? --------------------------------------------------------------------------- Command Prompt, Inc. wrote: > Currently we have the following working: > > Multiple server connection: 100% > SSL Connectivity for secure management: 100% > Over the Wire backup: 100% > Over the Wire restore: 100% > User management: 100% > Group Management: 100% > Query exectution: 50% > Database management: 75% > Table Management: 75% -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026
Hello, No. This is not Open Source Software (mentioned previously). At some point we may Open Source it, especially as Mammoth and Herd come to fruition but we have to make back our investment :) J On Mon, 18 Feb 2002, Bruce Momjian wrote: > > Is this open-source software? > > --------------------------------------------------------------------------- > > Command Prompt, Inc. wrote: > > Currently we have the following working: > > > > Multiple server connection: 100% > > SSL Connectivity for secure management: 100% > > Over the Wire backup: 100% > > Over the Wire restore: 100% > > User management: 100% > > Group Management: 100% > > Query exectution: 50% > > Database management: 75% > > Table Management: 75% > > -- -- by way of pgsql-general@commandprompt.com http://www.postgresql.info/ http://www.commandprompt.com/
Good day,
I have a client that was using a PL/pgSQL function called html_linebreaks
to translate newlines into (X)HTML <br/> tags, and he ran into a serious
memory issue today which actually brought down his Linux server. It looked
like this:
DECLARE
formatted_string text := '''';
BEGIN
IF $1 IS NULL THEN
RETURN '''';
END IF;
FOR i IN 0 .. length($1) LOOP
IF substr($1, i, 1) = ''\\n'' THEN
formatted_string := formatted_string || ''<br/>'';
ELSE
formatted_string := formatted_string || substr($1, i, 1);
END IF;
END LOOP;
RETURN formatted_string;
END;
Now, this obviously isn't the most efficient thing in the world, but on a
28k text field it quickly ate up his entire system's memory (over 300
megabytes) in a PostgreSQL 7.1.3 postmaster instance, and required a
reboot of the system to clean up after it.
Troubleshooting it a bit, it seemed that either the substr() or the
concat operator was never giving back the memory it was allocating for its
task.
I re-wrote the function for him in C as a shared object to avoid the
problem, but how exactly does PL/pgSQL manage the memory it requires for
calls to functions and operators? Is there any way to explicitly free
bytes you're done with before asking for more?
Also, does 7.2's version of PL/pgSQL behave the same way?
Regards,
Jw.
--
jlx@commandprompt.com, by way of pgsql-general@commandprompt.com
http://www.postgresql.info/
http://www.commandprompt.com/
"Command Prompt, Inc." <pgsql-general@commandprompt.com> writes:
> ... how exactly does PL/pgSQL manage the memory it requires for
> calls to functions and operators?
7.1 and before leak like a sieve :-(, at least for the duration of a
single function call.
> Also, does 7.2's version of PL/pgSQL behave the same way?
7.2 should be much better, though I am too lazy to try your specific
example right now. If you still see leakage under 7.2 please report it
and we'll try to fix it.
regards, tom lane
"Command Prompt, Inc." <pgsql-general@commandprompt.com> writes:
> I have a client that was using a PL/pgSQL function called html_linebreaks
> to translate newlines into (X)HTML <br/> tags, and he ran into a serious
> memory issue today which actually brought down his Linux server.
FWIW, I've now tried this in 7.2, and it doesn't seem to leak memory;
but it is unreasonably slow ... which is not too surprising considering
the number of cycles you are expending per byte. plpgsql is not a good
text-processing language. This function would be a one-liner in either
plperl or pltcl, and tremendously more efficient too.
regards, tom lane