On Fri, Apr 13, 2007 at 03:02:28PM +0200, Dany DeBontridder wrote:
> On 4/13/07, Heikki Linnakangas <[EMAIL PROTECTED]> wrote:
> >
> >Dany DeBontridder wrote:
> >> I'm working to implement a new feature to pg_dump: the ability to dump
> >> objects like function, indexes...
> >
> >pg_dump already du
On 4/13/07, Heikki Linnakangas <[EMAIL PROTECTED]> wrote:
Dany DeBontridder wrote:
> I'm working to implement a new feature to pg_dump: the ability to dump
> objects like function, indexes...
pg_dump already dumps functions and indexes.
Right but you can't dump only one or two functions or
Am Freitag, 13. April 2007 14:28 schrieb Dany DeBontridder:
> But, in that case, those functions are only usable for pg_dump, what about
> the rest of code ? We don't have a central location for those small
> reusable snippets of code ?
The main point of these functions is to catch errors and exit
Hi,
char *
pg_strcat (char *dest,char *src)
{
/* pg_realloc is a safer function than realloc */
dest=pg_realloc(dest,strlen(dest)+strlen(src)+1);
strcat(dest,src);
return dest;
}
Postgres already has something for the above functionality.
See makeStringInfo, appendStringInfo.
Regards,
Nik
Dany DeBontridder wrote:
I'm working to implement a new feature to pg_dump: the ability to dump
objects like function, indexes...
pg_dump already dumps functions and indexes.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
Hi,
I'm working to implement a new feature to pg_dump: the ability to dump
objects like function, indexes... And I notice that there some usefull
functions like pg_malloc, pg_calloc... So I've added pg_free to avoid the
sequence if-not-null-free-point-to-NULL, now I'd like to add a function
pg_st
