Custom color for fence, whisker and outliers in BoxWhiskerChart

I have trouble understanding this fallacy: "If A, then B. Therefore if not-B, then not-A."

Is "the fire consumed everything on its way" correct?

local storage : Uncaught TypeError: Cannot set property 'innerHTML' of null

After checking in online, how do I know whether I need to go show my passport at airport check-in?

Play Zip, Zap, Zop

Early credit roll before the end of the film

Why does photorec keep finding files after I have filled the disk free space as root?

Why would space fleets be aligned?

How does one write from a minority culture? A question on cultural references

What is the difference between rolling more dice versus fewer dice?

any clues on how to solve these types of problems within 2-3 minutes for competitive exams

Removing whitespace between consecutive numbers

How much mayhem could I cause as a fish?

Why do neural networks need so many training examples to perform?

Can you tell from a blurry photo if focus was too close or too far?

How to assess the long-term stability of a college as part of a job search

Citing paywalled articles accessed via illegal web sharing

Potential client has a problematic employee I can't work with

False written accusations not made public - is there law to cover this?

What is the difference between "...", '...', $'...', and $"..." quotes?

What language shall they sing in?

TikZ graph edges not drawn nicely

Am I a Rude Number?

How can I store a pdf in PostgreSQL

How can I insert if key not exist with PostgreSQL?IBM DB2 - store large filesHow to insert binary data into a PostgreSQL BYTEA column using libpqxx?Does having a big table that I do not query cause the whole DB to be slower?How to change the mount point for a column in postgresql table?Backup-strategy for redundant data in postgresql-db.Query for get column number in PostgreSQLHow can I retrieve the image which is stored in bytea column of a pg_toast schema?Store HTTP response in PostgreSQLChunking data into a PostgreSQL bytea column?

5

2

I have to store .pdf files in a table.

I have a table, state, with columns:

id_state,

name,

pdffile (bytea)

I want to store the pdf files in the pdffile column.

How can I do this?

postgresql insert blob

share|improve this question

edited May 25 '17 at 4:17

Evan Carroll

32.6k970222

asked Mar 12 '13 at 15:18

GiuliocasGiuliocas

26112

• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  ... and you're sure you don't want to store it in a file system location and have that location stored in the database (just for clarification and not for flame wars, just trying to ensure bases are covered)?
  
  – swasheck
  Mar 12 '13 at 15:30
  
  
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  Which programming language do you use? @swasheck: there are perfectly valid reasons to store this kind of things in a database. As with everything it has its advantages and disadvantages (I personally think it has more advantages than disadvantages).
  
  – a_horse_with_no_name
  Mar 12 '13 at 17:11
  
  
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  @a_horse_with_no_name: I know. As I said, I was just ensuring that this was the best course of action for OP's use case.
  
  – swasheck
  Mar 12 '13 at 17:45
  

  
  
  
  

add a comment | 

5

2

I have to store .pdf files in a table.

I have a table, state, with columns:

id_state,

name,

pdffile (bytea)

I want to store the pdf files in the pdffile column.

How can I do this?

postgresql insert blob

share|improve this question

edited May 25 '17 at 4:17

Evan Carroll

32.6k970222

asked Mar 12 '13 at 15:18

GiuliocasGiuliocas

26112

• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  ... and you're sure you don't want to store it in a file system location and have that location stored in the database (just for clarification and not for flame wars, just trying to ensure bases are covered)?
  
  – swasheck
  Mar 12 '13 at 15:30
  
  
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  Which programming language do you use? @swasheck: there are perfectly valid reasons to store this kind of things in a database. As with everything it has its advantages and disadvantages (I personally think it has more advantages than disadvantages).
  
  – a_horse_with_no_name
  Mar 12 '13 at 17:11
  
  
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  @a_horse_with_no_name: I know. As I said, I was just ensuring that this was the best course of action for OP's use case.
  
  – swasheck
  Mar 12 '13 at 17:45
  

  
  
  
  

add a comment | 

I have to store .pdf files in a table.

I have a table, state, with columns:

id_state,

name,

pdffile (bytea)

I want to store the pdf files in the pdffile column.

How can I do this?

postgresql insert blob

share|improve this question

edited May 25 '17 at 4:17

Evan Carroll

32.6k970222

asked Mar 12 '13 at 15:18

GiuliocasGiuliocas

26112

id_state,

name,

pdffile (bytea)

share|improve this question

edited May 25 '17 at 4:17

Evan Carroll

32.6k970222

asked Mar 12 '13 at 15:18

GiuliocasGiuliocas

26112

share|improve this question

edited May 25 '17 at 4:17

Evan Carroll

32.6k970222

asked Mar 12 '13 at 15:18

GiuliocasGiuliocas

26112

edited May 25 '17 at 4:17

Evan Carroll

32.6k970222

edited May 25 '17 at 4:17

Evan Carroll

32.6k970222

asked Mar 12 '13 at 15:18

GiuliocasGiuliocas

26112

asked Mar 12 '13 at 15:18

GiuliocasGiuliocas

26112

4 Answers
4

active

oldest

votes

2

First, I store PDF's in the db as bytea's. They are easier to manage than large objects and you really dont get very much out of the streaming API (now, streaming video, that should go into lobs). The one real problem with doing this is that it takes extra memory to unescape the data when it comes back to the database and you really can't stream it effectively.

The key thing is that you have to unescape the data when it comes back. libpq provides functions for that as do other programming languages. A few (like Perl) provide db drivers which automatically handle these cases.

You are on to the right structure here. Store it as a bytea and unescape it on retrieval.

share|improve this answer

answered Mar 20 '13 at 10:09

Chris TraversChris Travers

11k3889

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  This is a very abbreviated list of downfalls. It's not just streaming. It's the backend session stays tied while it's sending the file down to libpq as part of the resultset. Also, whatever other data is left on the row is likely also not ready to display until the PDF transfers. Parallel operations like https pipelining on pdf? You'll now have to tie up the database with one session per PDF.
  
  – Evan Carroll
  May 26 '17 at 8:17
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  But those are very use-specific downfalls. They don't apply, for example, where you are storing data for specific reasons where those are not applicable. For example wanting to store PDFs actually sent to a customer for tracking purposes. There are OLTP reasons why one might want to do so in an OLTP system.
  
  – Chris Travers
  May 26 '17 at 8:27
  

  
  
  
  

add a comment | 

2

To achieve this I have used the library lipq. It's the C API for postgresql.

const char *paramValues[2];

paramValues[0] = &your_id;

paramValues[1] = &binaryContentOfPdfFile;



res = PQexecParams(pConnection, "insert into my_table (id_state, pdffile)

VALUES ($1, $2);",

        2,       /* params */

        NULL,    /* let the backend deduce param type */

        paramValues,

        NULL,    /* don't need param lengths since text */

        NULL,    /* default to all text params */

        0);

Here is the postgresql mailing list thread I took the code from.

I guess it would be something not so different with other API like pyODBC or psqlODBC. It depends on the library you have chosen. You didn't say which API you use.

However: you should also consider storing only the URI/URL to the pdf file in your database.

share|improve this answer

edited 8 mins ago

answered Mar 12 '13 at 16:48

Stephane RollandStephane Rolland

2,30562136

add a comment | 

1

Probably the best way store PDF file in postgresql is via large object. You should have a table field of type OID. The create a large object with your PDF and then store the large object OID in the table.

Be careful with postgresql 9, since large object rights where defined. If you want to share access to the large object to many different postgresql users, you have to GRANT them the SELECT right. Please note that you cannot GRANT the DELETE right, so the owner is the one that must delete the object.

Moreover, special care should be done for maintaining storage: whenever you delete a large object, and you remove the OID from the table, the large object storage is not freed. You should run a command from contrib package, called vacuumlo, anche then the normal vacuumdb.

share|improve this answer

answered Mar 12 '13 at 23:45

eppesuigeppesuig

2,7571814

add a comment | 

0

Don't store PDFs in the database

There are no database features that can edit or process a PDF. Storing them is likely to lock up your db-session for extended periods. There is absolutely no reason whatsoever to do this. PostgreSQL is not a filesystem, it's a database.

share|improve this answer

answered May 25 '17 at 4:16

Evan CarrollEvan Carroll

32.6k970222

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  I disagree with you. PDFs are just values and being able to back up pdfs attached to database entities in the same backup is a good reason you might want to.
  
  – Chris Travers
  May 26 '17 at 7:45
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @ChrisTravers They're not just values: they're files. You can't seek through a value. You can always seek through a file. A value is a piece of data. A file, especially a pdf file, is an input for an external program. A database does not manage the display, a PDF encompasses display. Your RDBMS is not a backup management tool. You can easily back up the database and the filesystem at the same time.
  
  – Evan Carroll
  May 26 '17 at 8:04
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  If you want to seek, lobs in Postgres give you that. Usually it is not what you want in a db however.
  
  – Chris Travers
  May 26 '17 at 8:17
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  So have an accounting system. Want to track invoice pdfs as sent out, and guarantee that these are properly tracked to the transactions for auditing reasons. Why not store them in PostgreSQL. All we need to do is store them, retrieve them, and most importantly back up and restore them with the rest of the data? I.e. they are values for auditing purposes.
  
  – Chris Travers
  May 26 '17 at 8:24
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  No reason whatsoever is a dangerous statement and almost always wrong.
  
  – Chris Travers
  May 26 '17 at 8:25
  

  
  
  
  

 | 
show 2 more comments

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "182"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f36493%2fhow-can-i-store-a-pdf-in-postgresql%23new-answer', 'question_page');
}
);

Post as a guest

Name

Email

Required, but never shown

2

First, I store PDF's in the db as bytea's. They are easier to manage than large objects and you really dont get very much out of the streaming API (now, streaming video, that should go into lobs). The one real problem with doing this is that it takes extra memory to unescape the data when it comes back to the database and you really can't stream it effectively.

The key thing is that you have to unescape the data when it comes back. libpq provides functions for that as do other programming languages. A few (like Perl) provide db drivers which automatically handle these cases.

You are on to the right structure here. Store it as a bytea and unescape it on retrieval.

share|improve this answer

answered Mar 20 '13 at 10:09

Chris TraversChris Travers

11k3889

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  This is a very abbreviated list of downfalls. It's not just streaming. It's the backend session stays tied while it's sending the file down to libpq as part of the resultset. Also, whatever other data is left on the row is likely also not ready to display until the PDF transfers. Parallel operations like https pipelining on pdf? You'll now have to tie up the database with one session per PDF.
  
  – Evan Carroll
  May 26 '17 at 8:17
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  But those are very use-specific downfalls. They don't apply, for example, where you are storing data for specific reasons where those are not applicable. For example wanting to store PDFs actually sent to a customer for tracking purposes. There are OLTP reasons why one might want to do so in an OLTP system.
  
  – Chris Travers
  May 26 '17 at 8:27
  

  
  
  
  

add a comment | 

2

First, I store PDF's in the db as bytea's. They are easier to manage than large objects and you really dont get very much out of the streaming API (now, streaming video, that should go into lobs). The one real problem with doing this is that it takes extra memory to unescape the data when it comes back to the database and you really can't stream it effectively.

The key thing is that you have to unescape the data when it comes back. libpq provides functions for that as do other programming languages. A few (like Perl) provide db drivers which automatically handle these cases.

You are on to the right structure here. Store it as a bytea and unescape it on retrieval.

share|improve this answer

answered Mar 20 '13 at 10:09

Chris TraversChris Travers

11k3889

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  This is a very abbreviated list of downfalls. It's not just streaming. It's the backend session stays tied while it's sending the file down to libpq as part of the resultset. Also, whatever other data is left on the row is likely also not ready to display until the PDF transfers. Parallel operations like https pipelining on pdf? You'll now have to tie up the database with one session per PDF.
  
  – Evan Carroll
  May 26 '17 at 8:17
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  But those are very use-specific downfalls. They don't apply, for example, where you are storing data for specific reasons where those are not applicable. For example wanting to store PDFs actually sent to a customer for tracking purposes. There are OLTP reasons why one might want to do so in an OLTP system.
  
  – Chris Travers
  May 26 '17 at 8:27
  

  
  
  
  

add a comment | 

First, I store PDF's in the db as bytea's. They are easier to manage than large objects and you really dont get very much out of the streaming API (now, streaming video, that should go into lobs). The one real problem with doing this is that it takes extra memory to unescape the data when it comes back to the database and you really can't stream it effectively.

The key thing is that you have to unescape the data when it comes back. libpq provides functions for that as do other programming languages. A few (like Perl) provide db drivers which automatically handle these cases.

You are on to the right structure here. Store it as a bytea and unescape it on retrieval.

share|improve this answer

answered Mar 20 '13 at 10:09

Chris TraversChris Travers

11k3889

share|improve this answer

answered Mar 20 '13 at 10:09

Chris TraversChris Travers

11k3889

answered Mar 20 '13 at 10:09

Chris TraversChris Travers

11k3889

answered Mar 20 '13 at 10:09

Chris TraversChris Travers

11k3889

2

To achieve this I have used the library lipq. It's the C API for postgresql.

const char *paramValues[2];

paramValues[0] = &your_id;

paramValues[1] = &binaryContentOfPdfFile;



res = PQexecParams(pConnection, "insert into my_table (id_state, pdffile)

VALUES ($1, $2);",

        2,       /* params */

        NULL,    /* let the backend deduce param type */

        paramValues,

        NULL,    /* don't need param lengths since text */

        NULL,    /* default to all text params */

        0);

Here is the postgresql mailing list thread I took the code from.

I guess it would be something not so different with other API like pyODBC or psqlODBC. It depends on the library you have chosen. You didn't say which API you use.

However: you should also consider storing only the URI/URL to the pdf file in your database.

share|improve this answer

edited 8 mins ago

answered Mar 12 '13 at 16:48

Stephane RollandStephane Rolland

2,30562136

add a comment | 

2

To achieve this I have used the library lipq. It's the C API for postgresql.

const char *paramValues[2];

paramValues[0] = &your_id;

paramValues[1] = &binaryContentOfPdfFile;



res = PQexecParams(pConnection, "insert into my_table (id_state, pdffile)

VALUES ($1, $2);",

        2,       /* params */

        NULL,    /* let the backend deduce param type */

        paramValues,

        NULL,    /* don't need param lengths since text */

        NULL,    /* default to all text params */

        0);

Here is the postgresql mailing list thread I took the code from.

I guess it would be something not so different with other API like pyODBC or psqlODBC. It depends on the library you have chosen. You didn't say which API you use.

However: you should also consider storing only the URI/URL to the pdf file in your database.

share|improve this answer

edited 8 mins ago

answered Mar 12 '13 at 16:48

Stephane RollandStephane Rolland

2,30562136

add a comment | 

To achieve this I have used the library lipq. It's the C API for postgresql.

const char *paramValues[2];

paramValues[0] = &your_id;

paramValues[1] = &binaryContentOfPdfFile;



res = PQexecParams(pConnection, "insert into my_table (id_state, pdffile)

VALUES ($1, $2);",

        2,       /* params */

        NULL,    /* let the backend deduce param type */

        paramValues,

        NULL,    /* don't need param lengths since text */

        NULL,    /* default to all text params */

        0);

Here is the postgresql mailing list thread I took the code from.

I guess it would be something not so different with other API like pyODBC or psqlODBC. It depends on the library you have chosen. You didn't say which API you use.

However: you should also consider storing only the URI/URL to the pdf file in your database.

share|improve this answer

edited 8 mins ago

answered Mar 12 '13 at 16:48

Stephane RollandStephane Rolland

2,30562136

const char *paramValues[2];

paramValues[0] = &your_id;

paramValues[1] = &binaryContentOfPdfFile;



res = PQexecParams(pConnection, "insert into my_table (id_state, pdffile)

VALUES ($1, $2);",

        2,       /* params */

        NULL,    /* let the backend deduce param type */

        paramValues,

        NULL,    /* don't need param lengths since text */

        NULL,    /* default to all text params */

        0);

share|improve this answer

edited 8 mins ago

answered Mar 12 '13 at 16:48

Stephane RollandStephane Rolland

2,30562136

answered Mar 12 '13 at 16:48

Stephane RollandStephane Rolland

2,30562136

answered Mar 12 '13 at 16:48

Stephane RollandStephane Rolland

2,30562136

1

Probably the best way store PDF file in postgresql is via large object. You should have a table field of type OID. The create a large object with your PDF and then store the large object OID in the table.

Be careful with postgresql 9, since large object rights where defined. If you want to share access to the large object to many different postgresql users, you have to GRANT them the SELECT right. Please note that you cannot GRANT the DELETE right, so the owner is the one that must delete the object.

Moreover, special care should be done for maintaining storage: whenever you delete a large object, and you remove the OID from the table, the large object storage is not freed. You should run a command from contrib package, called vacuumlo, anche then the normal vacuumdb.

share|improve this answer

answered Mar 12 '13 at 23:45

eppesuigeppesuig

2,7571814

add a comment | 

1

Probably the best way store PDF file in postgresql is via large object. You should have a table field of type OID. The create a large object with your PDF and then store the large object OID in the table.

Be careful with postgresql 9, since large object rights where defined. If you want to share access to the large object to many different postgresql users, you have to GRANT them the SELECT right. Please note that you cannot GRANT the DELETE right, so the owner is the one that must delete the object.

Moreover, special care should be done for maintaining storage: whenever you delete a large object, and you remove the OID from the table, the large object storage is not freed. You should run a command from contrib package, called vacuumlo, anche then the normal vacuumdb.

share|improve this answer

answered Mar 12 '13 at 23:45

eppesuigeppesuig

2,7571814

add a comment | 

Probably the best way store PDF file in postgresql is via large object. You should have a table field of type OID. The create a large object with your PDF and then store the large object OID in the table.

Be careful with postgresql 9, since large object rights where defined. If you want to share access to the large object to many different postgresql users, you have to GRANT them the SELECT right. Please note that you cannot GRANT the DELETE right, so the owner is the one that must delete the object.

Moreover, special care should be done for maintaining storage: whenever you delete a large object, and you remove the OID from the table, the large object storage is not freed. You should run a command from contrib package, called vacuumlo, anche then the normal vacuumdb.

share|improve this answer

answered Mar 12 '13 at 23:45

eppesuigeppesuig

2,7571814

share|improve this answer

answered Mar 12 '13 at 23:45

eppesuigeppesuig

2,7571814

answered Mar 12 '13 at 23:45

eppesuigeppesuig

2,7571814

answered Mar 12 '13 at 23:45

eppesuigeppesuig

2,7571814

0

Don't store PDFs in the database

There are no database features that can edit or process a PDF. Storing them is likely to lock up your db-session for extended periods. There is absolutely no reason whatsoever to do this. PostgreSQL is not a filesystem, it's a database.

share|improve this answer

answered May 25 '17 at 4:16

Evan CarrollEvan Carroll

32.6k970222

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  I disagree with you. PDFs are just values and being able to back up pdfs attached to database entities in the same backup is a good reason you might want to.
  
  – Chris Travers
  May 26 '17 at 7:45
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @ChrisTravers They're not just values: they're files. You can't seek through a value. You can always seek through a file. A value is a piece of data. A file, especially a pdf file, is an input for an external program. A database does not manage the display, a PDF encompasses display. Your RDBMS is not a backup management tool. You can easily back up the database and the filesystem at the same time.
  
  – Evan Carroll
  May 26 '17 at 8:04
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  If you want to seek, lobs in Postgres give you that. Usually it is not what you want in a db however.
  
  – Chris Travers
  May 26 '17 at 8:17
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  So have an accounting system. Want to track invoice pdfs as sent out, and guarantee that these are properly tracked to the transactions for auditing reasons. Why not store them in PostgreSQL. All we need to do is store them, retrieve them, and most importantly back up and restore them with the rest of the data? I.e. they are values for auditing purposes.
  
  – Chris Travers
  May 26 '17 at 8:24
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  No reason whatsoever is a dangerous statement and almost always wrong.
  
  – Chris Travers
  May 26 '17 at 8:25
  

  
  
  
  

 | 
show 2 more comments

0

Don't store PDFs in the database

There are no database features that can edit or process a PDF. Storing them is likely to lock up your db-session for extended periods. There is absolutely no reason whatsoever to do this. PostgreSQL is not a filesystem, it's a database.

share|improve this answer

answered May 25 '17 at 4:16

Evan CarrollEvan Carroll

32.6k970222

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  I disagree with you. PDFs are just values and being able to back up pdfs attached to database entities in the same backup is a good reason you might want to.
  
  – Chris Travers
  May 26 '17 at 7:45
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @ChrisTravers They're not just values: they're files. You can't seek through a value. You can always seek through a file. A value is a piece of data. A file, especially a pdf file, is an input for an external program. A database does not manage the display, a PDF encompasses display. Your RDBMS is not a backup management tool. You can easily back up the database and the filesystem at the same time.
  
  – Evan Carroll
  May 26 '17 at 8:04
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  If you want to seek, lobs in Postgres give you that. Usually it is not what you want in a db however.
  
  – Chris Travers
  May 26 '17 at 8:17
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  So have an accounting system. Want to track invoice pdfs as sent out, and guarantee that these are properly tracked to the transactions for auditing reasons. Why not store them in PostgreSQL. All we need to do is store them, retrieve them, and most importantly back up and restore them with the rest of the data? I.e. they are values for auditing purposes.
  
  – Chris Travers
  May 26 '17 at 8:24
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  No reason whatsoever is a dangerous statement and almost always wrong.
  
  – Chris Travers
  May 26 '17 at 8:25
  

  
  
  
  

 | 
show 2 more comments

Don't store PDFs in the database

There are no database features that can edit or process a PDF. Storing them is likely to lock up your db-session for extended periods. There is absolutely no reason whatsoever to do this. PostgreSQL is not a filesystem, it's a database.

share|improve this answer

answered May 25 '17 at 4:16

Evan CarrollEvan Carroll

32.6k970222

share|improve this answer

answered May 25 '17 at 4:16

Evan CarrollEvan Carroll

32.6k970222

answered May 25 '17 at 4:16

Evan CarrollEvan Carroll

32.6k970222

answered May 25 '17 at 4:16

Evan CarrollEvan Carroll

32.6k970222