twaway23
Not in my country (in Europe). You get unemployment benefits for 2+ years that is a percentage of your salary up to a certain level. The maximum you can get is around $40k USD, which can be difficult because you probably have a mortgage and other expenses that were calibrated to a much higher salary.
You are also required to actively apply for jobs, and you may be required to take a job application course. I think you can even be assigned to a job interview if you delay. It is not intended as a "free" paid vacation. I think that even in some cases you are theoretically required to take any job anywhere in the country even if you have to move, but I haven't heard of anyone who had to do that. I assume they look at your social situation (family etc.)
After 2 years you are placed into a different type of program where you don't get a fixed amount, but you get money according to what the local government decides you need. That means you would need to sell your big house and move to a cheaper appartement if you want to get any support. If you had any savings, you would probably have to spend them before getting any assistance.
From the documentation it seems that each graph will use a separate "namespace" in Postgres. Are there any performance costs of switching namespaces for each query?
Or do you recommend that we use a single graph with a label per customer? This option seems like it could open up some security issues if some queries forget to add this label. By using a separate graph per customer, the query will need to have a valid graph name for a customer to return any data. If it is filtered by a label, you can easily forget to add it and think everything is OK because it actually returns results.