Jan Beseda writes:
> I'm having an issue with dropping a view as shown below:
> DROP VIEW access_group_view;
> ERROR: XX000: cache lookup failed for type 75083631
> LOCATION: format_type_internal, format_type.c:152
Does the behavior change if you say CASCADE?
The fact that it's failing in for
Hi there,
I'm having an issue with dropping a view as shown below:
DROP VIEW access_group_view;
ERROR: XX000: cache lookup failed for type 75083631
LOCATION: format_type_internal, format_type.c:152
I've also checked the source code here, which :
https://doxygen.postgresql.org/format__type_8c_s
Hi All,
not pgsql related, since I could not find an more general list I am writing on
-general, I hope this is ok.
We are at a phase of restructuring our software infrastructure, and I'd like to
ask you guys, what do you use for :
a) Issue/bug tracking, we used to have Bugzilla then youtrack,
On Thu, 14 Apr 2022 at 10:47, Steve Baldwin wrote:
> Ok, so you want to allow _other_ updates to a customer while this process
> is happening? In that case, advisory locks will probably work. The only
> consideration is that the 'id' is a bigint. If your customer id maps to
> that, great. If not
Ok, so you want to allow _other_ updates to a customer while this process
is happening? In that case, advisory locks will probably work. The only
consideration is that the 'id' is a bigint. If your customer id maps to
that, great. If not (for example we use UUID's), you will need some way to
conver
Hi Steve,
Thanks for your thoughts!
I was thinking to avoid using locks on the customer rows because there is a
lot of other unrelated access to that table. In particular I don’t want
writes to that table queueing up behind this process.
However, does the fact that you are suggesting row locks
Hi Perryn,
I don't know why you think advisory locks are the solution. It seems
regular row locks would ensure you have exclusive access to the customer.
Maybe something like this:
begin;
select * from customer where id = $1 for update skip locked;
if the query returns no rows it means something
Hi there,
We have identified a problem that we think advisory locks could help with,
but we wanted to get some advice on whether its a good idea to use them
this way (and any tips, best practices or gotchas we should know about)
THE PROBLEM
We have some code that does the following
- For
