Re: [GENERAL] pg_Restore

2013-01-30 Thread C. Bensend
> Don't know exactly the name of the ntfs property, if i remember well it's > recover point, but haven't used Windows for a while. I think you're talking about shadow copies. :) Benny -- "The very existence of flamethrowers proves that sometime, somewhere, someone said to themselves, 'You kn

Re: [GENERAL] POSTGRESQL Newbie

2012-03-21 Thread C. Bensend
> In short, MySQL offered the appearance of ease of use, which meant you > didn't need a DBA or even, really, to read the manual. For most > people it was good enough. It turned out that once you started trying > to scale it, you really did need all those features that the MySQL > 3.2.3 and earl

Re: [GENERAL] Backup complete

2011-07-27 Thread C. Bensend
> I take backup of postgres databases with pg_dump command. > But it didn't take backup of all sequences,views & functions in > different databases. > > I want to know how we can complete backup so we can get complete data > after restoring from a single file. > > I faced errors when dumping data

Re: [GENERAL] Oracle / PostgreSQL comparison...

2011-06-23 Thread C. Bensend
> http://cglendenningoracle.blogspot.com/2011/06/oracle-vs-postgres-postgresql.html > > Any comments? Amusing. " What kind of support is available if we have a problem? What is their patching schedule to address exploits and known security defects? If there is a bug, how responsive is the organi

Re: [GENERAL] Plpgsql function to compute "every other Friday"

2011-04-05 Thread C. Bensend
> By making this function sql and immutable, you give the database more > ability to inline it into queries which can make a tremendous > performance difference in some cases. You can also index based on it > which can be useful. Very nice, Merlin. These aren't really a concern in my case as I'

Re: [GENERAL] Plpgsql function to compute "every other Friday"

2011-04-04 Thread C. Bensend
> generate_series(date '2001-01-05', date '2020-12-31', interval '2 weeks') > > > will return every payday from jan 5 2001 to the end of 2020 (assuming > the 5th was payday, change the start to jan 12 if that was instead). And THERE is the winner. I feel like an idiot for not even considering ge

Re: [GENERAL] Plpgsql function to compute "every other Friday"

2011-04-04 Thread C. Bensend
> Not sure if your needs are like mine, but here is the function I use. It > stores the date in a config table, and rolls it forward when needed. It > also calculates it from some "know payroll date", which I'm guessing was > near when I wrote it? (I'm not sure why I choose Nov 16 2008.) for m

Re: [GENERAL] Plpgsql function to compute "every other Friday"

2011-04-04 Thread C. Bensend
> It is a very simplistic approach since you do not take into account > holidays. But if it meets your needs what you want is the modulo operator > ( > "%"; "mod(x,y)" is the equivalent function ) which performs division but > returns only the remainder. > > N % 14 = [a number between 0 and (14 -

[GENERAL] Plpgsql function to compute "every other Friday"

2011-04-04 Thread C. Bensend
Hey folks, So, I'm working on a little application to help me with my budget. Yeah, there are apps out there to do it, but I'm having a good time learning some more too. :) I get paid every other Friday. I thought, for scheduling purposes in this app, that I would take a stab at writing

Re: [GENERAL] How to add hosts to pg_hba.conf and postgresql.conf?

2011-03-15 Thread C. Bensend
> Explains why locahost is OK, but how do I get PM to listen on *.5432 Well, you believe you already have, by telling PostgreSQL to listen on '*'. There might be a few different reason why it's not: 1) Are you editing the correct postgresql.conf file? Do you have multiple ones on the filesy

Re: [GENERAL] How to add hosts to pg_hba.conf and postgresql.conf?

2011-03-15 Thread C. Bensend
> I'm trying to allow a remote host on our 10.3.55.X network remote access > to > a Postgres Database on the same network. > > We're running Solaris 10 with Postgres 83 > > My postgresql.conf looks like this; > > > listen_addresses = '*' # what IP address(es) to listen > on; >

Re: [GENERAL] Confusion about users and roles

2010-03-01 Thread C. Bensend
> Generally speaking you don't want to make per-user entries in > pg_hba.conf; it's just too much of a PITA for maintenance, unless > you really need different auth mechanisms for different users. > I'd suggest using "all" for the hba database and user columns whenever > possible. If you want con

[GENERAL] Confusion about users and roles

2010-02-28 Thread C. Bensend
Hey folks, I'm playing around with putting some of my email system's config into PostgreSQL, and I ran into some behavior I didn't expect today. I'm sure this is just misunderstanding on my part, but reading the documentation hasn't cleared it up for me yet. This is PostgreSQL 8.4.2 on Ope