Thread: Aggregate Functions Template
I need to create an aggregate function to do some math not currently provided by the available tools. Can someone point to an example aggregate function syntax that I can use as a template for my own function. I'm still a little green on some aspects of PostgreSQL and am drawing a blank on how to do this properly from scratch. Thanks for the help! Mark
Attachment
On Thu, May 19, 2005 at 03:17:07PM -0400, Mark Fenbers wrote: > > I need to create an aggregate function to do some math not currently > provided by the available tools. Can someone point to an example > aggregate function syntax that I can use as a template for my own > function. I'm still a little green on some aspects of PostgreSQL and am > drawing a blank on how to do this properly from scratch. The General Bits newsletter has a few examples that might be helpful, even if they're not quite what you're after: http://www.varlena.com/varlena/GeneralBits/109.php http://www.varlena.com/varlena/GeneralBits/4.html There are sure to be some examples in the list archives -- just search for "create aggregate": http://archives.postgresql.org/ If these links don't help, then please post more details about what you're trying to do and what trouble you're having. If you have any code that doesn't work the way you want but that helps show what you're after, then go ahead and post it with an explanation of what it does (or doesn't do) and what you'd like it to do (or not do). -- Michael Fuhr http://www.fuhr.org/~mfuhr/
Yes, your varlena links are what I was looking for as a source of help... Thanks! Mark Michael Fuhr wrote: >On Thu, May 19, 2005 at 03:17:07PM -0400, Mark Fenbers wrote: > > >>I need to create an aggregate function to do some math not currently >>provided by the available tools. Can someone point to an example >>aggregate function syntax that I can use as a template for my own >>function. I'm still a little green on some aspects of PostgreSQL and am >>drawing a blank on how to do this properly from scratch. >> >> > >The General Bits newsletter has a few examples that might be helpful, >even if they're not quite what you're after: > >http://www.varlena.com/varlena/GeneralBits/109.php >http://www.varlena.com/varlena/GeneralBits/4.html > >There are sure to be some examples in the list archives -- just >search for "create aggregate": > >http://archives.postgresql.org/ > >If these links don't help, then please post more details about what >you're trying to do and what trouble you're having. If you have >any code that doesn't work the way you want but that helps show >what you're after, then go ahead and post it with an explanation >of what it does (or doesn't do) and what you'd like it to do (or >not do). > > >
Attachment
Hi, Sqlers - I just installed 8.0.3, and am getting up to speed with the new features. First on my list is Tablespaces. In the docs, I see this: Note: There is usually not much point in making more than onetablespace per logical file system, since you cannot controlthelocation of individual files within a logical file system. However,PostgreSQL does not enforce any such limitation,and indeed it isnot directly aware of the file system boundaries on your system. Itjust stores files in the directoriesyou tell it to use. (http://www.postgresql.org/docs/8.0/interactive/manage-ag-tablespaces.html) I assume this is from the perspective of performance, correct? I was planning on doing a tablespace per logical project, as we internally structure most other things that way, and also to ease moving things around in the event we restructure filesystems, move things between servers, etc. In general, at least on our development machines, I was planning on using them to make data management easier. I note that I'm not seeing any Oracle style alter tablespace ... commands for moving things around, but it appears from that page that it is possible to do by changing the $PGDATA/pg_tblspc/$symlink and updating pg_tablespace (even if doing so is 'not recommended'). Is this a flawed use of tablespaces? Thanks, -j -- Jamie Lawrence jal@jal.org "Reality must take precedence over public relations, for nature cannot be fooled." - Richard P. Feynman