write banks - Search results in mailing lists
Mailing lists >> pgsql-general >> Thread
2024-10-18 19:44:26 | Re: Permissions for Newly Created User (Tom Lane)
writes: Yeah. To enlarge on that: if you are capturing SQL commands in the log file, they most likely contain all kinds of sensitive data --- think credit card numbers, bank
Mailing lists >> pgsql-general >> Thread
2024-02-29 22:51:11 | Re: Content for talk on Postgres Type System at PostgresConf (Tom Lane)
writes: It's nastier than that: the restriction is that the length in *characters* be the same in all rows. In a variable-width encoding like UTF8 the length in bytes can vary. This means
Mailing lists >> pgsql-general >> Thread
2022-09-30 03:24:59 | Re: Limiting the operations that client-side code can perform upon its database backend's (Bryn Llewellyn)
bank accounts. And I also do Internet shopping. I went through the usual steps to set myself up to use each of these. And I have no choice but to put my faith in their
Mailing lists >> pgsql-general >> Thread
2022-02-11 01:06:56 | Re: Can we go beyond the standard to make Postgres radically better? (Mladen Gogala)
banks (figures) so the transaction handling part was modeled after the banking business. When I've had my first course in SQL, back in 1988, I was given analogy with writing checks
Mailing lists >> pgsql-general >> Thread
2020-07-13 10:26:39 | Re: Doubt in mvcc (Francisco Olarte)
write 1200. Some things happens if both use select for update and/or use the adequate isolation levels to force the engine to use appropiate locks. BUT if both transactions do a select, wait
Mailing lists >> pgsql-general >> Thread
2020-06-09 23:35:40 | Re: Something else about Redo Logs disappearing (Peter)
banks and insurance shops) would usually run Informix or Oracle. Postgres is just my own private fancy. On Tue, Jun 09, 2020 at 03:42:48PM -0400, Stephen Frost wrote: ! * Peter (pmc@citylink.dinoex.sub.org) wrote: ! > This
Mailing lists >> pgsql-general >> Thread
2018-04-26 03:10:40 | RE: Postgresql database encryption (Ahmed, Nawaz)
bank account, you paycheck information, etc. things that should not exist outside of controls)... PS. You cannot simply take a drive from one machine to another, when doing proper RAID and LUKS encryption
Mailing lists >> pgsql-general >> Thread
2017-11-09 04:27:17 | Re: [GENERAL] Migrating money column from MS SQL Server to Postgres (Allan Kamau)
writes: The value in the offending insert is: 0.0 Why does Postgres decide that 0.0 is "double precision" (which is a weird name in my opinion -- why can't it just be double
Mailing lists >> pgsql-general >> Thread
2016-10-13 22:26:27 | Re: SERIALIZABLE and INSERTs with multiple VALUES (Thomas Munro)
bank_account values (1, 200) on conflict do nothing; (1) ...waits for tx2... (2) postgres=# commit; (2) COMMIT (1) INSERT 0 0 (1) postgres=# commit; (1) COMMIT If tx1 ran before tx2, then it would
Mailing lists >> pgsql-general >> Thread
2016-03-10 12:09:25 | Re: Plan to support predicate push-down into subqueries with aggregates? (Adam Brusselback)
write them in a way which would push everything down properly. The issue is, that I need that data to be able to join to that view from other smaller sets of data
Mailing lists >> pgsql-general >> Thread
2014-07-18 03:13:20 | Watching Views (Nick Guenther)
write some ad-hoc json-formatter that spits out exactly the columns it is interested in. I want something more like Cubes[1], where a user (or at least, some javascript
Mailing lists >> pgsql-general >> Thread >> Search in thread (2)
2014-05-20 10:39:18 | Re: postgres 9.2.4 - ERROR: invalid input syntax for type numeric: "" (Khangelani Gama)
Write_off_amount", (hp_acc.hpfin_int_ltd) as "AFC_LTD", hp_acc.hpfin_deb_ltd as "Debits_LTD", hp_acc.hpfin_crd_ltd as "Credits_LTD", hp_acc.hpfin_pay_ltd as "Payments
Mailing lists >> pgsql-general >> Thread
2013-03-17 05:24:25 | Re: How to use daterange type? (Christophe Pettus)
write selects that handle that: postgres=# SELECT count(*) postgres-# FROM generate_series(lower('[2012-09-01, 2012-12-24]'::daterange)::timestamp, upper('[2012-09-01, 2012-12-24]'::daterange)::timestamp, '1 day') as day postgres
Mailing lists >> pgsql-general >> Thread
2012-06-07 13:14:49 | Re: Memory Overcommit (Tom Lane)
write. About all the kernel can do is terminate that process, ie, OOM kill. The only way to be certain an OOM kill cannot happen is if you reserve N pages worth of memory/swap space
Mailing lists >> pgsql-general >> Thread
2012-03-24 04:27:54 | Re: PostgreSQL 64 Bit XIDs - Transaction IDs (Scott Marlowe)
writes per second and hundreds of thousands of reads to the cache layer per second. There are real world problems with redundancy and reliability to work out with VoltDB that are quite different from Postgresql