On Thu, 15 Aug, 2024, 9:18 pm Alban Hertroys, wrote:
>
> > On 15 Aug 2024, at 14:15, Lok P wrote:
>
> (…)
>
> > Hello Greg,
> >
> > In terms of testing on sample data and extrapolating, as i picked the
> avg partition sizeof the table (which is ~20GB) and i created a non
> partitioned table with
Hi,
I have some questions When doing pg_restore of backup of a database to a
NEW server.
Is there a way to ensure the data integrity is in tact, and user ID and
access works liked how it was in the old server?
How to properly handle the materialized views when backing up and restoring?
Thanks.
Hi Vince,
For validation of databases, you can use the following approach
/usr/pgsql-16/bin/pg_dump -d postgres -h localhost -p 5428 | md5sum >
/var/lib/pgsql/db1.txt
/usr/pgsql-16/bin/pg_dump -d postgres -h localhost -p 5420 | md5sum >
/var/lib/pgsql/db2.txt
diff db1.txt db2.txt
By executing abo
On Thu, Aug 22, 2024 at 7:06 AM Vince McMahon
wrote:
> Hi,
>
> I have some questions When doing pg_restore of backup of a database to a
> NEW server.
>
> Is there a way to ensure the data integrity is in tact, and user ID and
> access works liked how it was in the old server?
>
pg_restore is jus
That's great on small databases. Not so practical when they're big.
On Thu, Aug 22, 2024 at 7:10 AM Muhammad Usman Khan
wrote:
> Hi Vince,
> For validation of databases, you can use the following approach
>
> /usr/pgsql-16/bin/pg_dump -d postgres -h localhost -p 5428 | md5sum >
> /var/lib/pgsql
On Thu, Aug 22, 2024 at 6:24 AM Ron Johnson wrote:
> That's great on small databases. Not so practical when they're big.
>
> So - - - - what is the recommended procedure for 'large' databases?
(Might be useful to have a definition for what a large database is as
well.)
Regards
On Thu, Aug 22, 2024 at 8:49 AM o1bigtenor wrote:
>
>
> On Thu, Aug 22, 2024 at 6:24 AM Ron Johnson
> wrote:
>
>> That's great on small databases. Not so practical when they're big.
>>
>> So - - - - what is the recommended procedure for 'large' databases?
>
> (Might be useful to have a definiti
On Thu, Aug 22, 2024 at 8:03 AM Ron Johnson wrote:
> On Thu, Aug 22, 2024 at 8:49 AM o1bigtenor wrote:
>
>>
>>
>> On Thu, Aug 22, 2024 at 6:24 AM Ron Johnson
>> wrote:
>>
>>> That's great on small databases. Not so practical when they're big.
>>>
>>> So - - - - what is the recommended procedur
On Thu, Aug 22, 2024 at 8:49 AM o1bigtenor wrote:
>
>
> On Thu, Aug 22, 2024 at 6:24 AM Ron Johnson
> wrote:
>
>> That's great on small databases. Not so practical when they're big.
>>
>> So - - - - what is the recommended procedure for 'large' databases?
>
Use a real backup system like pgBack
On Thu, Aug 22, 2024 at 10:22 AM Greg Sabino Mullane
wrote:
> On Thu, Aug 22, 2024 at 8:49 AM o1bigtenor wrote:
>
>>
>>
>> On Thu, Aug 22, 2024 at 6:24 AM Ron Johnson
>> wrote:
>>
>>> That's great on small databases. Not so practical when they're big.
>>>
>>> So - - - - what is the recommended
On Thu, Aug 22, 2024 at 9:59 AM o1bigtenor wrote:
> On Thu, Aug 22, 2024 at 8:03 AM Ron Johnson
> wrote:
>
>> On Thu, Aug 22, 2024 at 8:49 AM o1bigtenor wrote:
>>
>>> On Thu, Aug 22, 2024 at 6:24 AM Ron Johnson
>>> wrote:
>>>
That's great on small databases. Not so practical when they're
On 8/22/24 04:06, Vince McMahon wrote:
Hi,
I have some questions When doing pg_restore of backup of a database to a
NEW server.
How large a backup?
Is there a way to ensure the data integrity is in tact, and user ID and
access works liked how it was in the old server?
As to user access,
On Tue, Aug 20, 2024 at 8:33 AM Greg Sabino Mullane wrote:
>
> On Tue, Jul 23, 2024 at 12:45 PM Avinash Vallarapu
> wrote:
>>
>> However, I do agree with Lawrence that it is impossible to prove whether it
>> is written by AI or a human.
>> AI can make mistakes and it might mistakenly point out
Hi, Adrian.
The largest one is 8 GB after compression.
I have a window of 8 hours to handle 30 GB total of backup at various sizes.
On Thu, Aug 22, 2024, 11:36 AM Adrian Klaver
wrote:
> On 8/22/24 04:06, Vince McMahon wrote:
> > Hi,
> >
> > I have some questions When doing pg_restore of back
> Posts should be technically and factually correct
agreed and period. no need qualify how the nonsense was created.
-john
On Thu, Aug 22, 2024 at 4:13 PM Robert Treat wrote:
>
> On Tue, Aug 20, 2024 at 8:33 AM Greg Sabino Mullane
> wrote:
> >
> > On Tue, Jul 23, 2024 at 12:45 PM Avinash Val
I'm digging into GiST indexes again, and ran into a helpful script here:
https://medium.com/postgres-professional/indexes-in-postgresql-5-gist-86e19781b5db
(This piece has shown up in many places in various versions.) I've adapted
the search a little, as I'd like to make it easier to explore avai
Morris de Oryx writes:
> What I'm hoping for is a function like
> get_opt_class_strategy_description(optclass, straregy_number) I've
> looked at the source a bit, and it seems that there is no such
> function, and that it might well be difficult to implement. The
> strategy numbers are, as far as
On 8/22/24 14:31, Vince McMahon wrote:
Hi, Adrian.
The largest one is 8 GB after compression.
I have a window of 8 hours to handle 30 GB total of backup at various sizes.
I assume by compression you mean using some form of pg_dump -Fc.
As to your timeline determining whether that can be met
After installing PostgreSQL on my Debian-12 machine, I typed 'postgres
--version' and got this msg:
*bash: postgres: command not found*
'psql --version', however, does work and gives me this message :
*psql (PostgreSQL) 16.3 (Debian 16.3-1.pgdg120+1)*
Obviously postgres is not in the path, but
After installing PostgreSQL on my Debian-12 machine, I typed 'postgres
--version' and got this msg:
*bash: postgres: command not found*
'psql --version', however, does work and gives me this message :
*psql (PostgreSQL) 16.3 (Debian 16.3-1.pgdg120+1)*
Obviously postgres is not in the path, but
On 8/22/24 17:36, Arbol One wrote:
After installing PostgreSQL on my Debian-12 machine, I typed 'postgres
--version' and got this msg:
*bash: postgres: command not found*
'psql --version', however, does work and gives me this message :
*psql (PostgreSQL) 16.3 (Debian 16.3-1.pgdg120+1)*
Obviou
On Thu, 2024-08-22 at 20:36 -0400, Arbol One wrote:
>
> After installing PostgreSQL on my Debian-12 machine, I typed
> 'postgres --version' and got this msg:
> bash: postgres: command not found
>
> 'psql --version', however, does work and gives me this message :
>
> psql (PostgreSQL) 16.3 (D
Adrian Klaver writes:
> On 8/22/24 17:36, Arbol One wrote:
>> After installing PostgreSQL on my Debian-12 machine, I typed 'postgres
>> --version' and got this msg:
>> *bash: postgres: command not found*
>> 'psql --version', however, does work and gives me this message :
>> *psql (PostgreSQL) 16.
On 8/22/24 19:21, Tom Lane wrote:
Adrian Klaver writes:
On 8/22/24 17:36, Arbol One wrote:
After installing PostgreSQL on my Debian-12 machine, I typed 'postgres
--version' and got this msg:
*bash: postgres: command not found*
'psql --version', however, does work and gives me this message :
*p
Hi Arbol,
You can try from the following commands:
dpkg-query -L postgresql-16
which psql
sudo find / -name "postgres" 2>/dev/null
On Fri, 23 Aug 2024 at 05:35, Arbol One wrote:
> After installing PostgreSQL on my Debian-12 machine, I typed 'postgres
> --version' and got this msg:
> *bash: pos
Hi Arbol,
Hope above response from Usman must have resolved your issue. You may also
try by finding any binary of PostgreSQL. e.g.
find /usr -name pg_ctl
/usr/local/pgsql/bin/pg_ctl
/usr/lib/postgresql/16/bin/pg_ctl
Regards,
Ikram
On Fri, Aug 23, 2024 at 9:33 AM Muhammad Usman Khan
wrote:
Hi Arbol,
Try to find any binary e.g.
find /usr -name pg_ctl
/usr/local/pgsql/bin/pg_ctl
/usr/lib/postgresql/16/bin/pg_ctl
find /usr -name psql
/usr/bin/psql
/usr/local/pgsql/bin/psql
/usr/lib/postgresql/16/bin/psql
Later you may create a symlink or add in PATH.
Hope this helps.
Regards,
I
On 8/22/24 21:57, Muhammad Ikram wrote:
Hi Arbol,
Try to find any binary e.g.
find /usr -name pg_ctl
/usr/local/pgsql/bin/pg_ctl
/usr/lib/postgresql/16/bin/pg_ctl
find /usr -name psql
/usr/bin/psql
/usr/local/pgsql/bin/psql
/usr/lib/postgresql/16/bin/psql
Later you may create a symlink or
On Thu, Aug 22, 2024 at 8:36 PM Arbol One wrote:
> After installing PostgreSQL on my Debian-12 machine, I typed 'postgres
> --version' and got this msg:
> *bash: postgres: command not found*
>
> 'psql --version', however, does work and gives me this message :
>
> *psql (PostgreSQL) 16.3 (Debian 1
Hi Arbol
Use this command and it will show all the files installed by the package.
dpkg-query -L postgresql-16
Regards
Kashif Zeeshan
On Fri, Aug 23, 2024 at 9:50 AM Muhammad Ikram wrote:
> Hi Arbol,
>
> Hope above response from Usman must have resolved your issue. You may also
> try by fin
On 2024-08-22 16:09:47 +0500, Muhammad Usman Khan wrote:
> For validation of databases, you can use the following approach
>
> /usr/pgsql-16/bin/pg_dump -d postgres -h localhost -p 5428 | md5sum >
> /var/lib/
> pgsql/db1.txt
> /usr/pgsql-16/bin/pg_dump -d postgres -h localhost -p 5420 | md5sum >
31 matches
Mail list logo