Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.databases.postgresql > #526 > unrolled thread

how do you make dev db small so easy on resources while keeping apps working?

Back to article view | Back to comp.databases.postgresql

Contents

  how do you make dev db small so easy on resources while keeping apps working? johannes falcone <visphatesjava@gmail.com> - 2013-12-07 14:18 -0800
    Re: how do you make dev db small so easy on resources while keeping apps working? Robert Klemme <shortcutter@googlemail.com> - 2013-12-17 22:45 +0100
      Re: how do you make dev db small so easy on resources while keeping apps working? johannes falcone <visphatesjava@gmail.com> - 2014-01-26 21:49 -0800
        Re: how do you make dev db small so easy on resources while keeping   apps working? Robert Klemme <shortcutter@googlemail.com> - 2014-03-06 23:02 +0100
          Re: how do you make dev db small so easy on resources while keeping apps working? johannes falcone <visphatesjava@gmail.com> - 2014-04-09 02:31 -0700

#526 — how do you make dev db small so easy on resources while keeping apps working?

how truncate tables without making app not work?

[toc] | [next] | [standalone]

#530

On 12/07/2013 11:18 PM, johannes falcone wrote:
> how truncate tables without making app not work?

Why do you believe that you will get meaningful replies to your one 
sentence questions that convey nothing?

Regards

	robert

[toc] | [prev] | [next] | [standalone]

#538

Hm

Lets say a production db is 800G.

Do people using postgresql have a QA and DEv db as big?

Or is there a way to make the qa n dev smaller?

I would think one way would be to cut from say 1 million users to 10.
And do same for say transaction table.
Leaving tables involving products intact.

What do you do ?

[toc] | [prev] | [next] | [standalone]

#543 — Re: how do you make dev db small so easy on resources while keeping apps working?

On 01/27/2014 06:49 AM, johannes falcone wrote:
> Hm
>
> Lets say a production db is 800G.
>
> Do people using postgresql have a QA and DEv db as big?
>
> Or is there a way to make the qa n dev smaller?
>
> I would think one way would be to cut from say 1 million users to 10.
> And do same for say transaction table.
> Leaving tables involving products intact.
>
> What do you do ?
>


Depends on the type of QA you want to do.

[toc] | [prev] | [next] | [standalone]

#544

On Thursday, March 6, 2014 2:02:16 PM UTC-8, Robert Klemme wrote:
> On 01/27/2014 06:49 AM, johannes falcone wrote:
> 
> > Hm
> 
> >
> 
> > Lets say a production db is 800G.
> 
> >
> 
> > Do people using postgresql have a QA and DEv db as big?
> 
> >
> 
> > Or is there a way to make the qa n dev smaller?
> 
> >
> 
> > I would think one way would be to cut from say 1 million users to 10.
> 
> > And do same for say transaction table.
> 
> > Leaving tables involving products intact.
> 
> >
> 
> > What do you do ?
> 
> >
> 
> 
> 
> 
> 
> Depends on the type of QA you want to do.

qa not performance testing

meaning simply the app works

then later in staging you do more real performance testing

[toc] | [prev] | [standalone]

Back to top | Article view | comp.databases.postgresql

csiph-web