On Wed, Mar 18, 2020 at 10:57:22AM -0300, Norberto Dellê wrote:
> This setup worked very well for a long time, but since we upgraded
> PostgreSQL to newer versions (10.x), sometimes it just skips archiving some
> wal files. This seems to happen mainly when the server is shut down.
> There's no mess
Thanks for the elaborate response.
I don't define many variables, basically only a single one.
We've implemented multi tenancy using row level policy and by utilizing the
SET LOCAL variable to pass the tenant id to enforce querying the right
tenant.
For example in the table "stuff" I have a colum
On Wed, Mar 18, 2020, 12:55 PM Michael Lewis wrote:
> work_type.work_type_key = work_type.work_type_key
>
> You've done a cross join.
>
You meant to do permitted_work.work_type_key = work_type.work_type_key I
expect
>
The three types of thing (permitted_work; employee; work_type) don’t stand in a
1:1 relationship with each other. You might have multiple work_types or
permitted_work for each employee, I’m guessing.
Each existing combination produces one row in the result. So an employee with
three permitted_w
work_type.work_type_key = work_type.work_type_key
You've done a cross join.
I am confused. given this view:
AS
SELECT
employee.id ,
work_type.type ,
permit ,
work_type.overhead ,
work_type.descrip
from
permitted_work
inner join employee on
employee.employee_key = permitted_work.employee_key
inner join work_type on
Do you have default fillfactor set on this table? If not, I would wonder if
reducing it to 50% or even 20% would allow many more HOT updates that would
reduce bloat.
Also, is there any period of lower activity on your system that you could
schedule a vacuum freeze for daily or weekly? I believe ha
On 3/18/20 6:57 AM, Justin King wrote:
Please reply to list also
Ccing list
Here are the settings, these are the only ones that are not set to
default with the exception of a few tables that have been overridden
with a different value due to lots of updates and few rows:
And those values are?
Kostya writes:
> However, once I run the following transaction
> BEGIN READ WRITE
> SET LOCAL session.my_tenant_id="f00";
> SELECT * FROM someTable;
> COMMIT;
> Then
> SELECT current_setting("session.my_tenant_id");
> will return an empty string "". Basically "session.my_tenant_id" becomes
> defi
Hi
I have a strange case in some PostgreSQL instances that I monitor. First
the software versions and setup of a specific one:
- Windows Server 2012 Foundation
- PostgreSQL 10.10 x64
- archive_command = 'copy% p "D: \\ backup \\ wal \\% f" / y'
This setup worked very well for a long tim
Hi
We are using dynamic settings via SET LOCAL for row level security.
I would like to clarify that I'm seeing the correct behaviour
I create a new session to the database, I run the following query:
SELECT current_setting("session.my_tenant_id");
I will get the following error:
pq: unrecognized
Working on a project that has an MS Access front end. I tend to use some
RAISE NOTICE messages to debug things. Turns out these are not propagated
through MS Access. RAISE EXCEPTIONS are, as a pop up.
Anyone know how to change this?
Realize it is a bit off topic for this list.
--
"They that wou
Hi,
Le mer. 18 mars 2020 à 04:14, David Gauthier a
écrit :
> Hi:
>
> psql (9.6.7, server 11.3) (linux)
>
> Is there a way to set all constraints on all tables of a DB and/or schema
> to be deferrable ? Or do I have to do them one-by-one ?
>
>
You have to do them one by one. Or write a DO script
>Laurenz Albe writes:
>> On Tue, 2020-03-17 at 19:57 +, Daniel Westermann (DWE) wrote:
>>
>>> >> is someone using temporary tablespaces on a RAM disk ? Any experiences
>>> >> with that?
>>> >> I did some quick tests and checked the archives but could not find any
>>> >> information that eith
14 matches
Mail list logo
