pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Production Database requirement
4+ messages / 4 participants
[nested] [flat]

* Production Database requirement
@ 2018-01-04 17:47  Azimuddin Mohammed <azimeiu@gmail.com>
  0 siblings, 3 replies; 4+ messages in thread

From: Azimuddin Mohammed @ 2018-01-04 17:47 UTC (permalink / raw)
  To: pgsql-admin@lists.postgresql.org; pgsql-general@postgresql.org

Hello All,
Can anyone please let me know

1. What is the hardware and software  requirement for postgressql to be
installed in production. We are planning to use postgres for hadoop
backend, to store user access info, metadata etc. So, it will not be high
transaction db, but we might see lost of reads to this db.

2. Can we use Vm's to run the Db? Is it recommended ?


Thanks in Advance!


-- 

Regards,
Azim


<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&...;
Virus-free.
www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&...;
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Re: Production Database requirement
@ 2018-01-04 17:58  Francis Santiago <santiagocfc@gmail.com>
  parent: Azimuddin Mohammed <azimeiu@gmail.com>
  2 siblings, 0 replies; 4+ messages in thread

From: Francis Santiago @ 2018-01-04 17:58 UTC (permalink / raw)
  To: Azimuddin Mohammed <azimeiu@gmail.com>; +Cc: pgsql-admin@lists.postgresql.org; pgsql-general@postgresql.org

2018-01-04 14:47 GMT-03:00 Azimuddin Mohammed <azimeiu@gmail.com>:

> Hello All,
> Can anyone please let me know
>
> 1. What is the hardware and software  requirement for postgressql to be
> installed in production. We are planning to use postgres for hadoop
> backend, to store user access info, metadata etc. So, it will not be high
> transaction db, but we might see lost of reads to this db.
>

the minimum requirements depend of use the your bds, you can start by 50GB
y,  memory 2 Gb, for example

>
> 2. Can we use Vm's to run the Db? Is it recommended ?
>

Yes, they can use VM'S

>
>
> Thanks in Advance!
>
>
> --
>
> Regards,
> Azim
>
>
>
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&...; Virus-free.
> www.avast.com
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&...;
> <#m_2540529285869011783_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>

^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Re: Production Database requirement
@ 2018-01-04 18:22  Vincenzo Romano <vincenzo.romano@notorand.it>
  parent: Azimuddin Mohammed <azimeiu@gmail.com>
  2 siblings, 0 replies; 4+ messages in thread

From: Vincenzo Romano @ 2018-01-04 18:22 UTC (permalink / raw)
  To: Azimuddin Mohammed <azimeiu@gmail.com>; +Cc: pgsql-admin@lists.postgresql.org, PostgreSQL General <pgsql-general@postgresql.org>

2018-01-04 18:47 GMT+01:00 Azimuddin Mohammed <azimeiu@gmail.com>:
> Hello All,
> Can anyone please let me know
>
> 1. What is the hardware and software  requirement for postgressql to be
> installed in production. We are planning to use postgres for hadoop backend,
> to store user access info, metadata etc. So, it will not be high transaction
> db, but we might see lost of reads to this db.

Your question makes little sense without any details about the data
and the application architecture.
Please elaborate more.
You'd elaborate more on these points in order to get some meaningful advise.

> 2. Can we use Vm's to run the Db? Is it recommended ?

There's nothing against virtualization apart the computing and I/O
limits it can pose.
In general, real hardware can provide for better performances.

> Thanks in Advance!
>
>
> --
>
> Regards,
> Azim
>
>
> Virus-free. www.avast.com



-- 
Vincenzo Romano - NotOrAnd.IT
Information Technologies
--
NON QVIETIS MARIBVS NAVTA PERITVS




^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Re: Production Database requirement
@ 2018-01-04 19:02  Michelle Konzack <linux4michelle@tamay-dogan.net>
  parent: Azimuddin Mohammed <azimeiu@gmail.com>
  2 siblings, 0 replies; 4+ messages in thread

From: Michelle Konzack @ 2018-01-04 19:02 UTC (permalink / raw)
  To: pgsql-general@lists.postgresql.org

Salam Mohammed,

Am DATE hackte Azimuddin Mohammed in die Tasten:
> Hello All,
> Can anyone please let me know
>
> 1. What is the hardware and software  requirement for postgressql to be
> installed in production. We are planning to use postgres for hadoop
> backend, to store user access info, metadata etc. So, it will not be high
> transaction db, but we might see lost of reads to this db.

It sound a only a little bit more what I have a s /etc/passwd, /etc/shadow,
/etc/groups and /etc/gshadow replacement...

I have exactly this too and it rund quiert well on a MiniITX with 1000MHz
and 1 GByte of memory which is 60% unused.  The Debian GNU/Linux 7.11
installation together with the postgresql database using less then
5 GByte...  Lets say, the whole thing would run an a 20 GByte HDD.

I manage currently 23.000 users with it...

And no, I do not use LDAP.

My webservices authenticate directly with the database server which is
hostet at a friendly ISP in Estonia.

> 2. Can we use Vm's to run the Db? Is it recommended ?

Yes of course.

> Thanks in Advance!
------------------------------------------------------------------------


-- 
Michelle Konzack
00372-54541400





^ permalink  raw  reply  [nested|flat] 4+ messages in thread


end of thread, other threads:[~2018-01-04 19:02 UTC | newest]

Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2018-01-04 17:47 Production Database requirement Azimuddin Mohammed <azimeiu@gmail.com>
2018-01-04 17:58 ` Francis Santiago <santiagocfc@gmail.com>
2018-01-04 18:22 ` Vincenzo Romano <vincenzo.romano@notorand.it>
2018-01-04 19:02 ` Michelle Konzack <linux4michelle@tamay-dogan.net>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox