Tag Info

New answers tagged

2

Memory related settings You've already addressed the key bottleneck for read heavy applications, that is, having sufficient RAM for caching. Just make sure you've set appropriately high values for shared_bufferes, work_mem, maintenance_work_mem, and effective_cache_size within your postgresql.conf file. Actually, there's a litany of good info in this ...


1

For example, I have a table which contains a column whose format is BLOB. The result I would like to get is to extract the content of the BLOB into CSV files. What is the most elegant method to do this? BCP OUT will be your best choice. Make sure your database has BLOB data (Image and/or TEXT datatypes). Also, select into should be set to TRUE ...


0

You can see max_allowed_packet to 1G in your session SET max_allowed_packet = 1073741824; You can do so because MySQL will not immediately allocate it. A packet can grow. Please note how it mentions this in the MySQL Documentation: The packet message buffer is initialized to net_buffer_length bytes, but can grow up to max_allowed_packet bytes when ...


1

Also worth reading: Best Practice in File Storage while Building Applications - Database (Blob Storage) Vs File System BLOB Storage as the Best Solution For better scalability. Although file systems are designed to handle a large number of objects of varying sizes, say files and folders, actually they are not optimized for a huge number (tens of ...


0

The main cost of handling the data is the I/O. You are doing approximately the same amount of I/O, whether it is in 4KB chunks in the OS (plus directory traversal) or 16KB chunks in InnoDB (plus indirect block lookup). The filesystem and InnoDB are cached in radically different ways; this may factor into a difference -- depending on how cacheable the blogs ...



Top 50 recent answers are included