| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Edson Richter <edsonrichter(at)hotmail(dot)com>, Kevin Grittner <kgrittn(at)gmail(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Overhead changing varchar(2000) to text |
| Date: | 2015-12-15 02:27:35 |
| Message-ID: | 566F7A97.50601@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 12/9/15 5:43 PM, Edson Richter wrote:
> Actually, the biggest change is that I don't have to keep another
> constraint between app and database - if I want to increase the user
> perceived space, now I just have to change the application (of course,
> under the limits).
For what it's worth, I usually put some limit on fields that a webapp
can write to in the database. That way a bug in the app (or malicious
action) can't just start allocating gigabytes of stuff in your database.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2015-12-15 02:31:48 | Re: Feature Request: Faceting for full text search |
| Previous Message | Jim Nasby | 2015-12-15 02:24:56 | Re: HELP!!! The WAL Archive is taking up all space |