pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Richard Bernstein <richb201@gmail.com>
To: pgsql-admin@postgresql org <pgsql-admin@postgresql.org>
Subject: Image crud for Postgresql in php?
Date: Mon, 15 Jun 2020 06:07:36 -0400
Message-ID: <yjhudg7qi4wquf251orbkll8.1592215656002@email.android.com> (raw)

I have been attempting to add an image crud using postgresql to my php app. I use a local copy of mysql for the admin data but wanted to use a remotely hosted copy of postgres for the images. After a lot of effort it is clear that the image crud I am using doesn't support being hosted in a second database. Does anyone know of a php callable image crud that uses Postgresql?

On June 8, 2020, at 22:43, Peter <pmc@citylink.dinoex.sub.org> wrote:


Actually, the affair had some good side: as usual I was checking                
my own designs first and looking for flaws, and indeed I found one:             
                                                                                
If you do copy out the archive logs not directly to tape, but to                
some disk area for further processing, then there is an issue with              
possible loss. If you do it like the docs say, with a command like              
this:                                                                           
                                                                                
archive_command = 'test ! -f /mnt/server/archivedir/%f && cp %p                 
+/mnt/server/archivedir/%f'  # Unix                                             
                                                                                
That "cp" is usually not synchronous. So there is the possibility               
that this command terminates successfully, and reports exitcode zero            
back to the Postgres, and then the Postgres will consider that log              
being safely away.                                                              
                                                                                
But the target of the copy may not yet been written to disk. If                 
at that point a power loss happens, the log may become missing/damaged/         
incomplete, while the database may or may not consider it done                  
when restarting.                                                                
                                                                                
Therefore, mounting such a target filesystem in all-synchronous mode            
might be a good idea. (UFS: "-o sync", ZFS: "set sync=always")                  
                                                                                
cheerio,                                                                        
PMc                                                                             




Message-ID: <yjhudg7qi4wquf251orbkll8.1592215656002@email.android.com>
Permalink:  ../yjhudg7qi4wquf251orbkll8.1592215656002@email.android.com/
Also on:    postgresql.org/message-id/yjhudg7qi4wquf251orbkll8.1592215656002@email.android.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: richb201@gmail.com
  Subject: Re: Image crud for Postgresql in php?
  In-Reply-To: <yjhudg7qi4wquf251orbkll8.1592215656002@email.android.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

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