Re: [GENERAL] database size changed after restoring using pg_restore

On 11/8/2017 2:59 PM, Dylan Luong wrote: Hi I am upgrading some databases from a PostgreSQL 9.2 server to a new PostgreSQL 9.6 server. I used pg_dump and pg_restore for the upgrade. . But when I listed the size of the database (postgres=# \l+) between the 9.2 and the upgraded 9.6, the

Re: [GENERAL] database size changed after restoring using pg_restore

På onsdag 08. november 2017 kl. 23:59:40, skrev Dylan Luong < dylan.lu...@unisa.edu.au >: Hi I am upgrading some databases from a PostgreSQL 9.2 server to a new PostgreSQL 9.6 server.   I used pg_dump and pg_restore for the upgrade.   This is the command I us

Re: [GENERAL] Database size on disk

On Mon, Oct 5, 2015 at 12:47 PM, Quiroga, Damian wrote: > Hi, > > > > I’m looking for some advice on how to determine the DB size on disk to > trigger some cleanup tasks (deleting old data) if some threshold is reached. > > > > Let’s say that for simplicity I don’t want to ask for the size on dis

Re: [GENERAL] Database size

On 12/01/2010 2:00 AM, Leonardo M. Ramé wrote: A customer of mine asked me to periodically delete old, unneeded records containing ByteA fields, because he think it will reduce the database size on disk. Is this true?. For example, in Firebird, the database size is not reduced until you do a Back

Re: [GENERAL] Database size

Leonardo M. Ramé wrote: A customer of mine asked me to periodically delete old, unneeded records containing ByteA fields, because he think it will reduce the database size on disk. Is this true?. For example, in Firebird, the database size is not reduced until you do a Backup-Restore of the datab

Re: [GENERAL] Database size

On 11/01/2010 18:00, Leonardo M. Ramé wrote: > A customer of mine asked me to periodically delete old, unneeded records > containing ByteA fields, because he think it will reduce the database > size on disk. Is this true?. For example, in Firebird, the database size > is not reduced until you do a

Re: [GENERAL] Database size

Francisco Reyes wrote: I say "don't believe" because I don't recall if byteA was stored in the table itself or was stored outside using TOAST.. so I am not sure about how/when space is released for it. like all other data, that depends on the size of the data.if the entire row (tuple) is

Re: [GENERAL] Database size

Leonardo M. Ramé writes: A customer of mine asked me to periodically delete old, unneeded records containing ByteA fields, because he think it will reduce the database size on disk. Is this true?. No. For example, in Firebird, the database size is not reduced until you do a Backup-Restore of

Re: [GENERAL] Database size

Leonardo M. Ramé wrote: A customer of mine asked me to periodically delete old, unneeded records containing ByteA fields, because he think it will reduce the database size on disk. Is this true?. For example, in Firebird, the database size is not reduced until you do a Backup-Restore of the datab

Re: [GENERAL] database size grows (even after vacuum (full and analyze))....

Title: RE: [GENERAL] database size grows (even after vacuum (full and analyze)) Ok. I get the point. I'm using 7.2 because that's the one I got from the original Fedora Core 3 CD's. I'll upgrade to the most recent. Thank you all for your support. jmf -

Re: [GENERAL] database size grows (even after vacuum (full and analyze))....

Bruno Wolff III <[EMAIL PROTECTED]> writes: > In the long run, you should upgrade. 7.2 is essentially without support. I > beleive there is still a RHEL version using it that is in support, so a > critical fix might get back ported. No, Red Hat never shipped a RHEL version using 7.2.* (they went s

Re: [GENERAL] database size grows (even after vacuum (full and analyze))....

On Mon, 2006-05-08 at 18:07, Bruno Wolff III wrote: > Please keep replies copied to the list so that others can learn from and > contribute to the discussion. I don't remember where this was, but it looks > like general is probably reasonable. Sorry. I didn't notice. I'll keep that in mind. > >

Re: [GENERAL] database size grows (even after vacuum (full and analyze))....

Please keep replies copied to the list so that others can learn from and contribute to the discussion. I don't remember where this was, but it looks like general is probably reasonable. On Mon, May 08, 2006 at 15:02:20 +0100, Joao Miguel Ferreira <[EMAIL PROTECTED]> wrote: > Bruno and all, > >

Re: [GENERAL] Database Size Limiting

Campano, Troy wrote: Is it possible to have a database spread across two data files? So if it fills up filesystem1 then we could add a second filesystem and allow it to grow onto this second filesystem? If you're using Linux there is a tool called the Linux Volume Manager (LVM) which does this. Yo

Re: [GENERAL] Database Size Limiting

Title: Database Size Limiting I wonder if this will work:   each DB should assigned a diffrent user with set of premissions ( including insert ).   a script that can revoke the inseret privilage will emarge from time to time to check the DB size.   --Canaan Surfing Ltd.

Re: [GENERAL] Database Size Limiting

3:23 PM To: Joshua D. Drake Cc: Campano, Troy; Postgres general mailing list Subject: Re: [GENERAL] Database Size Limiting Joshua D. Drake wrote: > Hello, > > You could use Filsystem quotas but I strongly suggest against it as it > will probably bring about database corruption.

Re: [GENERAL] Database Size Limiting

Joshua D. Drake wrote: Hello, You could use Filsystem quotas but I strongly suggest against it as it will probably bring about database corruption. Ah - manual reference http://www.postgresql.org/docs/current/static/disk-full.html "24.2. Disk Full Failure The most important disk monitoring task of

Re: [GENERAL] Database Size Limiting

Joshua D. Drake wrote: Hello, You could use Filsystem quotas but I strongly suggest against it as it will probably bring about database corruption. I thought we handled that? I'm not saying it'd be pleasant, but I think it's no worse than a power-outage. Hmm, can't find anything in the manuals t

Re: [GENERAL] Database Size Limiting

ke [mailto:[EMAIL PROTECTED] Sent: Thursday, May 27, 2004 2:12 PM To: Campano, Troy Cc: Postgres general mailing list Subject: Re: [GENERAL] Database Size Limiting Hello, You could use Filsystem quotas but I strongly suggest against it as it will probably bring about database corruption. A bette

Re: [GENERAL] Database Size Limiting

Hello, You could use Filsystem quotas but I strongly suggest against it as it will probably bring about database corruption. A better solution would be to monitor the space being allocated so you can add storage as required. Sincerely, Joshua D. Drake Campano, Troy wrote: --> Is there a way to li

Re: [GENERAL] Database Size Limiting

Campano, Troy wrote: Is there a way to limit the size that an individual database can take up? My understanding is that all your databases go into a file system which is your 'catalog cluster'. But all the databases can grow until that filesystem is full. Is there a way to limit how big a database

Re: [GENERAL] Database Size

jackie wrote: Hello EveryBody How could I get the size(MB) of the Database du  on the datadirectory where the database are located. Feite