On Fri, Jun 10, 2016 at 12:49 PM, Francisco Olarte <fola...@peoplecall.com> wrote:
> I may be wrong but ... > > On Fri, Jun 10, 2016 at 6:33 PM, Sridhar N Bamandlapally > <sridhar....@gmail.com> wrote: > > One thing we can restrict to "begin noarchive" transaction block are > DELETE > > and SELECT only > > On 10 Jun 2016 21:57, "Sridhar N Bamandlapally" <sridhar....@gmail.com> > > wrote: > >> This is what I feel will give me solution to maintain production > >> (current+7days) and archive(current+history) without any etl/scheduler > > It seems ( to me ) you have a grossly underspecificied ( in the list ) > problem and you have invented an even more underspecified keyword to > magically solve it, and expect someone to develop it. > > And you haven't even bothered to avoid top posting, which is frowned > upon on this list and makes infering your problems solution even more > difficult. > > If you want to have something like this you'll need to post much more > details on what you are proposing, what are the use cases for the > general public, etc.. Just eyeballing it I would estimate this will > need many pages just to state the problems and the intended semantics > of your proposal. > > Regards. > Francisco Olarte. > > > -- > Sent via pgsql-general mailing list (pgsql-general@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-general > Please, you should specify your PostgreSQL version and O/S for questions like this. As a solution to your problem, have you considered using a VIEW with a WHERE clause similar to WHERE your_date > current_date - interval '7 days' ? -- *Melvin Davidson* I reserve the right to fantasize. Whether or not you wish to share my fantasy is entirely up to you.
